SiteAuditLint checklist library
What this checklist covers
A JavaScript SEO checklist confirms that frameworks like React, Next.js, Vue, and Angular deliver crawlable HTML, real links, correct metadata, proper status codes, and stable rendering for search engines and AI crawlers.
It is organized into 10 sections: Rendering Approach, HTML Content, Links, Metadata, Structured Data, Lazy Loading, Navigation, Status Codes, Hydration and Testing. Each check lists exactly what to verify and a priority, so you can work through the highest impact items first.
For background on the concepts behind these checks, see JavaScript SEO course, JavaScript SEO guide, JavaScript rendering.
Who it is for:
Download the javascript seo checklist
Use the interactive version below, or download it to share with your team, attach to tickets, or work through offline.
JavaScript SEO Checklist
Work through each check
0 of 12 checks complete
Rendering Approach
HTML Content
Links
Metadata
Structured Data
Lazy Loading
Status Codes
Hydration
Testing
Progress is saved in this browser only.
Detailed explanations
Each section below explains what to check, why it matters, the problems you will usually find, how to fix them, and how to confirm the fix.
Rendering Approach
What to check:
- Check rendering mode. SSR, SSG or hydration strategy documented.
Why it matters: Google renders JavaScript, but rendering is delayed, resource limited, and not guaranteed. Many AI crawlers do not render JavaScript at all. Content, links, and SEO tags that only appear after scripts run are at risk of being missed.
Common problems:
- Main content injected only on the client
- Links implemented as buttons or onClick handlers
- Titles, canonicals, or meta robots changed by JavaScript
- Single page app routes returning 200 for missing pages
How to fix it: Server render or statically generate critical content and tags, use real anchor links with URLs, and return proper status codes from the server.
How to verify: Compare raw HTML with rendered HTML for each template. Titles, H1s, main content, canonicals, and links should be present in the raw response.
Learn more: JavaScript SEO course, Rendering lesson, JavaScript links lesson, JavaScript SEO guide.
How SiteAuditLint helps: it checks rendering approach across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
HTML Content
What to check:
- Check raw HTML content. Main content exists in initial HTML.
Why it matters: Google renders JavaScript, but rendering is delayed, resource limited, and not guaranteed. See the earlier section on this topic for common problems.
How to verify: Compare raw HTML with rendered HTML for each template. Titles, H1s, main content, canonicals, and links should be present in the raw response.
How SiteAuditLint helps: it checks html content across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Links
On this checklist: check link markup. Explained in full in the On-Page SEO Checklist.
Metadata
On this checklist: check titles in HTML; check canonicals; check robots directives. Explained in full in the On-Page SEO Checklist.
Structured Data
On this checklist: check schema output. Explained in full in the On-Page SEO Checklist.
Lazy Loading
What to check:
- Check lazy-loaded content. Content loads without scroll or interaction.
Why it matters: Google renders JavaScript, but rendering is delayed, resource limited, and not guaranteed. See the earlier section on this topic for common problems.
How to verify: Compare raw HTML with rendered HTML for each template. Titles, H1s, main content, canonicals, and links should be present in the raw response.
How SiteAuditLint helps: it checks lazy loading across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Navigation
What to check:
- Check JS navigation. Routes have unique crawlable URLs, not hash fragments.
Why it matters: Google renders JavaScript, but rendering is delayed, resource limited, and not guaranteed. See the earlier section on this topic for common problems.
How to verify: Compare raw HTML with rendered HTML for each template. Titles, H1s, main content, canonicals, and links should be present in the raw response.
How SiteAuditLint helps: it checks navigation across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Status Codes
On this checklist: check SPA status codes. Explained in full in the Technical SEO Checklist.
Hydration
What to check:
- Check hydration errors. No content mismatch between server and client.
Why it matters: Google renders JavaScript, but rendering is delayed, resource limited, and not guaranteed. See the earlier section on this topic for common problems.
How to verify: Compare raw HTML with rendered HTML for each template. Titles, H1s, main content, canonicals, and links should be present in the raw response.
How SiteAuditLint helps: it checks hydration across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Testing
What to check:
- Compare source vs rendered. Diff shows no missing SEO elements.
Why it matters: Robots.txt controls which paths crawlers may request. It is the fastest way to block an entire site by accident. It also governs access for AI crawlers, so it is now part of your AI search visibility strategy as well as your traditional SEO.
Common problems:
- A staging Disallow: / rule deployed to production
- CSS and JavaScript blocked, stopping Google from rendering pages
- Overly broad wildcard patterns blocking important directories
- Missing or outdated sitemap declaration
How to fix it: Keep robots.txt minimal, block only what you truly need to keep out of crawlers, allow rendering resources, and declare your XML sitemap with an absolute URL.
How to verify: Fetch /robots.txt on production, test a list of key URLs against the live rules for Googlebot and each AI user agent, and confirm the file returns 200.
Learn more: Robots.txt lesson, Robots.txt and AI crawlers guide, Blocked by robots.txt issue, Missing robots.txt issue.
How SiteAuditLint helps: it checks testing across every crawled URL instead of one page at a time and lists exactly which URLs are affected.
Common mistakes
Client side rendering for indexable content
Links built as buttons
Soft 404s in single page apps
Metadata changed after hydration
Not comparing source and rendered HTML
When to run the checklist
- When choosing a rendering approach
- Before launching a JavaScript framework site
- After framework upgrades
- When rendered pages are missing from the index
How to verify fixes
Save a baseline crawl before you change anything. Fix high-priority and template-level issues first, since one template fix resolves many URLs, then re-crawl with the same start URL and settings and compare the two audits with audit comparison. Finally, confirm important pages in Search Console with URL Inspection. See how to prioritize audit findings.
SiteAuditLint workflow
Most checks in this list run automatically in a SiteAuditLint crawl. Use audit comparison to diff crawls and scheduled audits to monitor for regressions.
All SEO checklists
See the full checklist library, with a guide to choosing the right checklist for each job.