Technical SEO Checklist
A technical SEO checklist for websites that keep changing
Use this SiteBoost editorial checklist before launches, after migrations and during maintenance. Each item includes what to inspect and why the check matters.
How to use this checklist
Do not treat every item as equally urgent. First identify the public page types that support discovery or important user journeys. Test representative URLs, record evidence, and prioritize problems that repeat across templates. A single template error affecting hundreds of pages usually deserves attention before a cosmetic warning on one URL.
Keep search-engine controls and application controls separate. A SaaS site naturally has login, dashboard, payment and status routes, but those screens are not a substitute for crawlable public content. Public guides and landing pages should provide value without requiring an account.
Foundation checklist
Reachability
Open representative public URLs and confirm they return the intended content without broken redirect loops, authentication gates or unexpected errors.
Why it matters: Check more than the homepage. Sample important templates because a routing or deployment problem may affect only one section.
Index controls
Review robots meta directives and other index controls against the purpose of each page type.
Why it matters: Public editorial and landing pages normally need to be discoverable, while account, dashboard, checkout and private utility screens should not be treated as search content.
Canonical URLs
Confirm that each important page identifies the intended preferred URL and that canonical signals are not contradictory.
Why it matters: Watch for a shared template accidentally pointing many distinct pages to the homepage or another unrelated URL.
Sitemap quality
Keep the sitemap focused on canonical public pages that you genuinely want crawled and indexed.
Why it matters: Do not use a sitemap as a dump of every application route. Remove private, transactional, duplicate, error and low-value utility URLs.
Titles and descriptions
Write metadata that accurately distinguishes one page from another instead of mechanically swapping a keyword in a shared sentence.
Why it matters: Review template-generated metadata in batches so repeated problems can be fixed at their source.
Heading and content structure
Use a clear primary heading and supporting sections that help a reader understand the page.
Why it matters: A valid H1 does not make thin content useful; the body still needs original explanation, evidence, examples or practical guidance.
Internal links
Give important pages meaningful paths from navigation and related content.
Why it matters: Look for orphan pages and stale links after migrations. Contextual links should help a visitor continue a task or learn a related topic.
Images and media
Give informative images useful alternative text and deliver media at sensible dimensions and weight.
Why it matters: Decorative assets do not need keyword-heavy alt text. Optimize for accessibility and page experience rather than stuffing search phrases.
Mobile usability
Check readable text, usable controls, viewport behavior and navigation on smaller screens.
Why it matters: Test real interactions such as menus and forms; a responsive screenshot alone does not prove the page is usable.
Post-deploy verification
After every important technical fix, test the production URL and repeat the affected check.
Why it matters: Record what changed and what passed afterward. A merged commit is not evidence that the live site behaves correctly.
Prioritize template-wide problems
When one technical rule affects many URLs, solve the generating rule instead of editing pages one by one. Common examples include shared canonical logic, global metadata, navigation, robots directives and media components. Recheck several URLs after the template fix to make sure it did not solve one page while breaking another.
Use severity, reach and confidence to order the work. A high-confidence indexing block on an important template is usually more urgent than a speculative optimization with no measurable effect.
Separate verification from ranking expectations
A technical audit can verify whether a directive, link, response or page element is present and behaving as expected. It cannot guarantee a particular search position. After a fix, first verify the live technical state. Then observe search performance over an appropriate period without claiming that one change alone caused every movement.