SEO & technical health

Read the finding#

Open the SEO or Technical view and inspect the affected URL, severity, evidence and recommended action. A short title, duplicated headline or performance issue should point to a specific page or observation.

A recommendation is not a guarantee of ranking improvement. Prioritize issues according to the page’s purpose, traffic, severity and the effort required to verify a fix.

Work through a fix#

1. Verify the issue on the affected page and confirm it is still current.
2. Check the intended title, description, canonical or content against the page’s real purpose.
3. Ask the SEO or Coding agent for a proposed change with its reasoning.
4. Review any code diff and run the project’s checks before merging or deploying.
5. Recheck the page after delivery and wait for the relevant source to refresh before judging the result.

Keep the boundary clear#

Generating schema, robots.txt or a redirect map does not install it. A GitHub connection does not authorize every repository or automatic merging. Technical changes can affect indexing and traffic; keep a rollback path and involve the responsible site owner.

Lab performance tests vary by conditions. Treat a single result as a useful observation, not a permanent score for every visitor.