A clear diagnosis. A practical order of work.

Start with the pages that support revenue

We map core services, important landing pages and customer actions before reviewing the site. For a San Francisco practice, that may mean service and booking pages; for a software business, it may mean product, use-case and comparison pages.

• Agree on priority services and markets
• Record the current site structure and available search data
• Identify the people responsible for implementation

Turn findings into tickets your team can use

Each recommendation should name the affected URLs, describe the observed issue and explain how to verify the fix. A crawl warning alone is not a business priority.

• Discovery: response codes, robots rules, indexing and canonical consistency
• Content: intent gaps, duplication and missing decision information
• Experience: navigation, mobile readability and contact paths

Choose a sensible implementation sequence

Fix problems that prevent important pages from being reached first. Improve the pages with demonstrated demand next. Group template changes so one fix can help many pages, and document tradeoffs when the team has limited capacity.

What the handoff includes

The proposed audit scope can include an executive summary, a URL-level issue register and an implementation backlog. Confirm crawl scope, analytics access, the number of templates reviewed and whether follow-up verification is included before starting.