Technical SEO
Make important pages easier to reach and use.
Find issues that make your website harder to crawl, understand, or use. Prioritize indexing, redirects, internal links, mobile usability, and performance where they affect important pages.
Follow an important URL from end to end
A technical review should connect a reported issue to a page and a customer journey. Check whether the page resolves, whether its content is available, and whether its links and metadata describe the intended destination.
Separate a confirmed defect from a tool recommendation. Priorities should consider impact, affected pages, and the risk of changing a working system.
Typical review areas
- Response status, redirects, canonical URLs, and indexing directives.
- Internal navigation, missing pages, and broken links.
- Mobile layout, keyboard navigation, and readable content.
- Image delivery, unnecessary scripts, and important-page performance.
Plan changes around the existing stack
Understand the CMS, theme, plugins, hosting, and release process before choosing an implementation. Preserve working URLs and content while resolving the defect.
Keep a recoverable version and a record of the affected routes. A successful build alone does not establish that the correct domain serves the intended pages.
Measure comparable conditions
Compare the same pages, device profile, and test conditions before and after a change. Lab measurements are useful diagnostics; they do not replace evidence from real visitors.
Make the scope tangible
What useful work leaves behind.
Use these examples to define deliverables with a provider. They describe the work to agree, without promising a result.
- An affected-URL inventory
- List the exact URLs and observed response, canonical, indexing or navigation problem. A reproducible example is more useful than an unexplained score.
- An implementation specification
- Describe the intended behavior in the existing stack, the component responsible and the dependent pages that need review.
- A verification record
- Attach the tested revision, route checks and comparison conditions. Keep the accepted current version available while reviewing a replacement.
What should your website do better?
Start with your website, your service area, and the business goals you want search to support.