Shane’s Technical Site Audit · Practical guide

A Practical Technical SEO Check Before Publishing

Review the page-structure signals that help search engines and people understand a web page.

A page title and meta description should describe the actual page, not repeat a generic company slogan. Check that the page has a useful main heading, a viewport declaration for mobile and a canonical URL when appropriate. Confirm Open Graph titles describe the content people will share.

Meaningful images need useful alternative text; decorative images should not create noise for assistive technology. Review links for descriptive wording and check that important destinations are valid. A heading hierarchy should make the page easy to scan.

Correct missing or duplicated titles, unclear headings, broken links and absent image descriptions before polishing minor details. Then review the rendered page on a phone and with keyboard navigation.

Shane’s Technical Site Audit checks pasted HTML or an uploaded HTML file for title and description tags, H1 count, viewport, canonical URL, Open Graph title, image alt text and links. It does not crawl live URLs, execute scripts or measure page performance.

Start with the page a visitor and crawler actually receive

Choose one representative URL and inspect the HTML that is delivered for that page. Confirm that the title and description are specific, that there is one clear main heading, and that the viewport declaration supports mobile layouts. Check whether the canonical URL identifies the preferred version rather than a redirect, query-string variant or unrelated page.

Review Open Graph title and description for social sharing, image alternative text for meaningful images and descriptive anchor text for important links. A page can have valid tags and still be difficult to use, so inspect the rendered layout, keyboard focus, contrast and mobile navigation separately.

Fix high-impact issues first

Prioritize broken links, missing or duplicate titles, empty descriptions, unclear headings and missing alternative text on meaningful images. Then review structured data, language declarations and indexability directives. Do not add schema merely to increase the amount of markup; use only types and properties that accurately describe visible page content.

Keep a record of the URL, date checked, issue, evidence and proposed fix. After making a change, recheck the page that was affected. A one-page audit cannot establish that every route on a website is healthy.

Know the scope of the current audit tool

Shane’s Technical Site Audit checks pasted HTML or an uploaded HTML file for common title, description, heading, viewport, canonical, Open Graph, image-alt and link signals. Its separate live-page feature reads one public URL and uses a credit per page. It is not a full-site crawler, JavaScript browser, accessibility certification or Core Web Vitals test.

Put the workflow into practice

Explore Shane’s Technical Site Audit in BeVisibleHQ and use the process above with your own verified information.

Open Shane’s Technical Site Audit →

Improve answer-engine and generative visibility

Explore practical, evidence-based approaches to Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO). Neither approach guarantees AI citations or rankings.