When a business website receives little organic traffic, the first recommendation is often “publish more content.” Sometimes that is correct. Sometimes the existing content is already trapped behind technical problems that make the site difficult to crawl, index or understand.

A technical SEO audit examines the foundation beneath the words on the page. It answers questions such as:

• Can search engines reach the pages that matter?

• Are the right pages eligible for indexing?

• Does the website identify one preferred version of each page?

• Can important content be rendered and understood?

• Are internal links communicating a clear hierarchy?

• Does the mobile experience load and respond well?

• Can results be measured in qualified leads rather than rankings alone?

This 12-step checklist covers the highest-value issues for most small-business websites.

1. Confirm That Google Can Find the Website

Begin with Google Search Console. Review the Pages report, sitemap status and URL Inspection results for several important pages.

Check whether:

• The homepage is indexed

• Core service pages are indexed

• Important location pages are indexed

• Recent articles have been discovered

• Search Console reports server or redirect errors

• Pages are excluded for an understandable reason

Do not assume that every page should be indexed. Thank-you pages, account screens, internal search results and duplicate filter URLs may have no value in search. The objective is to make the right pages discoverable and keep low-value URLs from creating noise.

A simple site:yourdomain.com search can provide a rough view, but it is not a complete index report. Use Search Console for diagnosis.

2. Review Robots.txt and Noindex Directives

Robots.txt manages crawler access. A noindex directive controls whether a crawlable page should appear in search results. They are not interchangeable.

Google specifically warns that robots.txt is not a reliable way to keep a web page out of its index. A blocked URL can still appear when other pages link to it, and a crawler cannot see a noindex directive on a page it is forbidden to crawl.

Look for:

• Important directories blocked in robots.txt

• CSS or JavaScript files blocked when needed for rendering

• Production pages carrying a staging noindex

• Development or test environments exposed to crawling

• Private content that should be protected by authentication

Use the Google robots.txt guide when reviewing the rules.

If the audit is part of a rebuild, connect these findings to a complete plan for redesigning the website without losing SEO.

3. Validate the XML Sitemap

An XML sitemap tells search engines which canonical URLs you consider important and can help them crawl the site more efficiently.

The sitemap should:

• Return a 200 status

• Contain only canonical, indexable URLs

• Use the preferred HTTPS hostname

• Exclude redirected and broken URLs

• Exclude pages marked noindex

• Update when important content changes

• Be listed in Search Console

A sitemap is a discovery aid, not a command or ranking shortcut. Google describes sitemap submission as a hint, not a guarantee that every URL will be crawled or indexed.

4. Resolve Duplicate URLs and Canonical Conflicts

The same content may be available through multiple addresses because of:

• HTTP and HTTPS versions

• www and non-www hostnames

• Trailing-slash differences

• Tracking parameters

• Print views

• Product filters

• CMS-generated archives

• Uppercase and lowercase paths

Choose a preferred version and make the signals consistent.

For each indexable page, confirm that:

• The canonical tag points to the preferred URL

• Internal links use that preferred URL

• The XML sitemap lists that preferred URL

• Alternate versions redirect or canonicalize appropriately

• Canonical tags do not point to broken or irrelevant pages

Conflicting signals force search engines to decide which version is authoritative. A clean implementation removes that ambiguity.

5. Fix Broken Pages, Soft 404s and Redirect Chains

Crawl the website and group URLs by status code.

200: Successful Pages

Confirm these pages contain the expected content. Some broken experiences still return a 200 status, creating a soft 404.

301 or 308: Permanent Redirects

Use these when a page has moved permanently. Update internal links to point directly to the final destination.

302 or 307: Temporary Redirects

Use these only when the change is genuinely temporary.

404 or 410: Removed Pages

A true not-found response is appropriate when no relevant replacement exists. Customize the 404 page so visitors can recover through navigation, search or contact information.

Remove redirect chains and loops. A request should not bounce through multiple obsolete URLs before reaching its destination.

6. Make the Site Architecture Understandable

A visitor should be able to understand what the business does and reach an important service page without guessing. Search engines need the same clarity.

A small-business architecture often follows a simple hierarchy:

• Home

• Services

• Individual service pages

• Locations or service areas

• Work or case studies

• About

• Blog or resources

• Contact

Avoid burying profitable services several levels deep or relying on site search to reveal them. Important pages should be reachable through ordinary navigation and contextual links.

Google recommends crawlable <a> elements with href attributes. Interfaces built entirely around JavaScript click handlers can make discovery less reliable.

7. Audit Internal Links and Anchor Text

Internal links help visitors move between related information and help search engines understand page relationships.

Check for:

• Orphaned pages with no internal links

• Broken internal links

• Important pages receiving very few links

• Generic anchor text such as “click here”

• Repetitive keyword-heavy anchor text

• Links that still pass through redirects

• Articles that never connect to a service page

Use concise, descriptive link text. “See our technical SEO services” is more useful than “learn more.”

Google's link best-practices guide notes that every page you care about should receive a link from at least one other page on the site.

8. Improve Page Titles, Descriptions and Headings

Every important page needs a unique title that accurately describes its purpose. Include the service and location when they genuinely help a searcher understand the page.

Review:

• Duplicate page titles

• Missing or generic titles

• Titles that exceed the visible result unnecessarily

• Missing H1 headings

• Multiple H1s used without a clear structure

• Headings chosen for visual size rather than hierarchy

• Meta descriptions duplicated across the site

Meta descriptions are not a guarantee of the snippet Google will display, but a useful description can help a searcher decide whether the page fits their need.

Do not force keywords into every heading. Clear structure and useful language matter more than repeating a phrase mechanically.

9. Measure Core Web Vitals With Real-User Data

Core Web Vitals evaluate three parts of the user experience:

• Largest Contentful Paint measures loading performance.

• Interaction to Next Paint measures responsiveness.

• Cumulative Layout Shift measures visual stability.

Google's current thresholds for a good experience are:

MetricGood thresholdLargest Contentful Paint2.5 seconds or lessInteraction to Next Paint200 milliseconds or lessCumulative Layout Shift0.1 or less

These thresholds should be evaluated at the 75th percentile of page visits, separated across mobile and desktop where possible. Review Google's Web Vitals documentation for the measurement model.

Common small-business performance problems include:

• Oversized hero images

• Video loaded before it is needed

• Too many plugins

• Third-party chat and tracking scripts

• Unused CSS and JavaScript

• Web fonts that block rendering

• Layouts without reserved image dimensions

• Slow hosting or database queries

Do not optimize only for a laboratory score. Field data reflects the devices, connections and interactions of actual visitors.

10. Test Mobile Rendering and Interaction

Google uses the mobile version of content for indexing. More importantly, many customers search for local services from a phone while they are ready to call, book or request an estimate.

Test whether:

• The same important content appears on mobile and desktop

• Navigation works with touch and keyboard

• Phone numbers are easy to activate

• Forms fit the screen and use appropriate input types

• Buttons and links have usable target sizes

• Text can be read without zooming

• Sticky elements do not cover content

• Images do not push calls to action far below the fold

• Popups can be dismissed

Responsive design is not complete when a desktop layout merely shrinks. The task must remain easy on a small screen.

11. Validate Structured Data

Structured data gives search engines explicit information about a page and can make content eligible for supported rich-result features.

Commonly relevant types include:

• Organization

• LocalBusiness

• Service

• Article

• BreadcrumbList

• Product

• Event

• VideoObject

Use the type that accurately matches visible content. Do not mark up reviews, prices, questions or services that do not appear on the page.

Google generally recommends JSON-LD when the platform supports it because it is easier to maintain. Validate markup with the Rich Results Test and monitor enhancement reports in Search Console. Structured data can improve understanding and eligibility; it does not guarantee a rich result or ranking.

See Google's structured-data introduction for current requirements.

12. Confirm That Leads Can Be Measured

Technical SEO should connect search visibility to business outcomes.

Verify tracking for:

• Contact-form submissions

• Click-to-call actions

• Appointment bookings

• Estimate requests

• Purchases

• Qualified lead status

• Service requested

• Geographic area

• Revenue when available

Test the events yourself. A dashboard can report zero conversions because the website is failing, or because the tracking is broken.

Rankings and traffic are diagnostic metrics. Qualified leads and revenue determine whether the work supports the business.

How to Prioritize Technical SEO Problems

An audit may uncover hundreds of warnings. Treating every warning as equally urgent wastes time.

Prioritize in this order:

Critical: Access and Indexation

Fix blocked service pages, accidental noindex directives, server errors, broken canonicals and failed migrations first.

High: Revenue and Reach

Fix problems affecting high-traffic pages, profitable services, lead forms, local landing pages and mobile performance.

Medium: Understanding and Efficiency

Improve internal linking, duplicate content, structured data, titles and crawl efficiency.

Low: Isolated Cleanup

Resolve minor issues with little user or search impact after the foundation is stable.

Severity, affected traffic and business value should drive the backlog—not the number of items a tool labels as warnings.

What a Technical SEO Audit Should Deliver

A useful audit is not a 100-page export from a crawler. It should provide:

• An executive summary in plain language

• Evidence for each finding

• Affected URLs or templates

• Recommended remediation

• Priority and estimated effort

• The expected user or business impact

• Clear ownership

• A validation plan

The final step is implementation. Identifying a problem without assigning and verifying the fix does not improve search performance.

Build the Foundation Before Publishing More

Content strategy works best when the website beneath it is crawlable, fast, organized and measurable.

Redkey Web Design audits crawl paths, indexation, Core Web Vitals, structured data, internal linking and conversion tracking, then helps implement the repairs. Explore our SEO and digital growth services or request a site audit to find the technical issues creating the greatest drag on qualified organic traffic.