Confirm discovery and indexation first
A content plan cannot compensate for important URLs that are blocked, redirected incorrectly, duplicated, orphaned, or canonicalized elsewhere. Build a bounded URL inventory and compare intended pages with what search engines can actually discover.
- Robots directives and XML sitemap coverage
- Canonical targets and duplicate routes
- Redirect chains, loops, and retired URLs
- Status codes and soft-error patterns
- Internal links to priority pages
Check the rendered document
Source HTML alone is not enough for JavaScript-heavy sites. Verify the rendered title, description, headings, content, links, structured data, and canonical. Record meaningful differences between server and client output.
Validate structure against visible content
Schema should describe what a reader can see. Organization, product, article, author, and breadcrumb markup can clarify relationships, but invalid or inflated markup creates ambiguity rather than authority.
Turn findings into controlled changes
A technical finding becomes useful when it names the affected resource, expected state, exact proposed change, risk, owner, verification test, and rollback path.