Technical SEO Audit Checklist for a Business Website
Audit crawlability, HTTPS, sitemaps, canonical URLs, internal linking, structured data, performance and lead measurement.
Discuss your project on WhatsApp ↗Confirm crawlability before optimizing content
Check whether your domain resolves publicly, the server returns a successful response and search-engine crawlers can retrieve the page. Inspect robots.txt, meta robots directives, X-Robots-Tag headers and login restrictions. An XML sitemap should be an actual XML document at the submitted address. If Google reports that it cannot fetch the sitemap, test the public URL, DNS and HTTP response before editing keywords.
Remove ambiguity about preferred URLs
Choose a canonical URL for each distinct page. Avoid publishing the same content at multiple parameter or hostname variants without a clear preferred version. Use relevant permanent redirects when old pages are replaced. Check that canonical tags do not point to unrelated destinations or URLs that return errors. The sitemap should list pages you intend Google to index, not every file on the server.
Improve the usefulness of each page
Write page titles that reflect actual services, use one clear primary topic and answer the practical questions customers ask before they buy. Link related services, guides and examples in a natural hierarchy. Review mobile readability, image alternatives and loading behavior. Structured data should describe the visible, truthful content on the page; it does not substitute for useful content.
Measure outcomes, not just impressions
Separate discovery metrics such as impressions and indexed pages from business metrics such as qualified inquiries and sales conversations. Verify that click tracking does not imply a submitted inquiry if a visitor only opened WhatsApp. Keep a change log so you can compare search impressions, conversions and crawling behavior after meaningful site updates.
Practical checklist
- DNS and HTTPS publicly work
- Key pages return 200 and useful HTML
- robots.txt and meta robots allow intended pages
- Sitemap parses and contains canonical URLs
- Headings, titles and descriptions are distinct
- No broken internal navigation paths
- Relevant schema matches visible content
- Analytics distinguishes clicks from completed leads
Frequently asked questions
Why does Search Console say Couldn't fetch?
Common causes include inaccessible DNS, network/server errors, the wrong URL, authentication, or an unexpected server response. Test the exact public URL first.
Should every tag or search result get its own page?
No. Create a page only when it serves a distinct reader need with substantive information.
Turn a plan into a practical project.
Share your goals and receive a scoped conversation, not an automatic price guarantee.
Start a conversation ↗