SEO report for www.irs.gov
https://www.irs.gov/ · checked Sun, 01 Nov 2026 17:26 GMT
Fix these first
- Title tagcritical
“Internal Revenue Service | An official website of the United States government”
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
Also fixes: Entity clarity
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- Render-blocking resourceshigh
3 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Imagesmedium
19 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- Topic focushigh
5 of 8 title keywords appear in the main content (missing: internal, revenue, website).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to irs.gov…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap index found at https://www.irs.gov/sitemap.xml listing 12 sitemaps.
Declared in robots.txt.
Most recent lastmod: 2026-10-30T18:02:27-04:00.
- ✓
Canonical URLhigh
Canonical: https://www.irs.gov/
Points to this page (self-referencing).
- ✓
Redirectshigh
1 redirect before the page loaded.
https://irs.gov/ → https://www.irs.gov/
A single redirect to your preferred address is normal; just make sure your own links use the final address.
- ✓
www / non-wwwmedium
irs.gov redirects to www.irs.gov.
- ✓
hreflangmedium
8 hreflang link(s).
All language codes are valid.
No x-default (recommended for a language picker or fallback page).
Search snippet & sharing 50%
How the page looks in Google results and when shared.
- ✗
Title tagcritical
“Internal Revenue Service | An official website of the United States government”
About 693px of Google's ~580px desktop width – it will probably be cut off.
Fix: Write a unique title of roughly 50–60 characters with the main search phrase first.
- ✓
Meta descriptionhigh
151 characters, ~947px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 47%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
1,151 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 56 (fairly easy), about 9 words per sentence.
- !
Topic focushigh
5 of 8 title keywords appear in the main content (missing: internal, revenue, website).
Fix: Use your main title phrases naturally in the opening paragraph and headings.
- ✗
H1 headingcritical
No H1 heading.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
71 headings for 1151 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- !
Text-to-code ratiolow
8% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 56%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- !
Question-led contentmedium
2 heading(s) phrased as questions, e.g. “Do more with an IRS account”.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✓
Trust pages (E-E-A-T)medium
Links found to all three: about, contact and privacy.
Structured data 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
237 internal and 30 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “overview”, “individuals”, “what you can do with an account”, “contact us”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 67%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
720 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- ✓
HTML sizemedium
144 kB of HTML.
- ✓
Compressionmedium
Compressed with br.
- ✗
Render-blocking resourceshigh
3 blocking script(s) and 2 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✓
Scripts & third partiesmedium
10 script tag(s); files loaded from 2 other domain(s): googletagmanager.com, static.addtoany.com.
- ✗
Imagesmedium
19 image(s).
19 without width/height – can cause layout shift (CLS).
14 image(s) after the first three aren't lazy-loaded.
0 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: public, max-age=86400
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 92%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=31536000
- ✗
Security headerslow
Present: nosniff, clickjacking protection.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✓
Server fingerprintlow
No X-Powered-By header (server: cloudflare).
Mobile & accessibility 92%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1, shrink-to-fit=no
- !
Image alt textmedium
2 of 19 images have no alt attribute.
Fix: Describe each meaningful image in its alt attribute (use alt="" for decorative ones).
- ✓
Form labelsmedium
All 7 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✓
Tap-to-contactmedium
One-tap contact: phone.
Local SEO 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
A UK phone number is shown.
No postcode found (fine for service-area businesses).
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.