How to run a 30-minute SEO audit for a new website
Check access, indexability, page identity, answer quality, and internal links in that order. The result is a short evidence-backed fix list, not a generic score.
Written for a founder or site owner preparing to promote a recently launched website with limited search data.
Key facts
- A short audit should find decisions the owner can act on, not produce a long list of unweighted observations.
- Crawl and indexing blockers take priority because copy changes cannot help a page that search systems cannot use.
- The final three fixes need a public URL, evidence, expected result, owner, and retest date.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
The direct answer
Spend six minutes on each of five areas: response and crawl access, canonical and indexing signals, title and visible page identity, answer quality, and internal links. Capture evidence from one important page in each area. Rank the final issues by whether they block access, confuse page identity, or weaken the reader's next action, then assign one owner and verification check to the first three fixes. The finished work should let a reader or reviewer identify the subject, the intended result, the evidence behind the recommendation, and the next action without reconstructing your reasoning. Keep material conditions in the same passage as the claim they limit. Use the canonical public page as the source of truth, since search engines and answer systems retrieve pages rather than private briefs. Google describes useful, reliable, people-first content and ordinary search eligibility as the foundation for both search results and its AI features. No heading pattern or schema type can compensate for a page that gives a vague answer, hides its evidence, or serves a different intent from its title. Complete the task for one named reader first, then check how the result appears to crawlers and extraction tools.
- A short audit should find decisions the owner can act on, not produce a long list of unweighted observations.
- Crawl and indexing blockers take priority because copy changes cannot help a page that search systems cannot use.
- The final three fixes need a public URL, evidence, expected result, owner, and retest date.
Prepare the page and evidence before editing
Choose the homepage, the main conversion page, and one representative article or directory record. Open each URL in a signed-out session and fetch the raw response. Gather access to Search Console when available, but do not let missing history prevent the public-page checks. Save a baseline before you change anything: the public URL, response status, canonical, visible title, main heading, opening answer, source links, and the date you checked them. Record the target question in the reader's words and write one sentence describing the decision the page supports. This baseline prevents a common measurement error where several edits ship together and nobody can tell which one improved the result. It also gives editors a compact source ledger. A reviewer can compare each material statement with the cited page, its jurisdiction or product version, and its checked date. If the task affects a generated template, inspect several representative URLs rather than assuming one record proves the template works for every content shape.
- List the three URLs and the business action each page should support.
- Record current response, canonical, robots directive, title, H1, and first visible answer.
- Open the XML sitemap and confirm that the selected canonical URLs appear there.
Complete the process in five controlled steps
Work through the five steps in order and keep one output from each step. The order protects you from polishing copy while a crawl, canonical, intent, or evidence problem still blocks the page. Each output should be small enough for another person to verify from the public URL. Use plain labels and stable entity names throughout the page. When a changing fact controls the answer, cite the primary source beside that fact and include the relevant date or version. After each step, compare the output with the primary question. Remove any section that serves a different reader decision, and link to a separate guide when the adjacent task deserves its own page. This creates a focused answer instead of a broad page assembled from loosely related keywords.
- 1. Test access: Fetch each URL without cookies, follow redirects, and check whether robots controls allow crawling and indexing. Evidence of completion: The final URL returns a usable response and exposes its main content.
- 2. Confirm identity: Compare the final URL, canonical, sitemap entry, title, H1, Open Graph URL, and structured-data URL. Evidence of completion: All identity signals name one production URL and one page subject.
- 3. Read the answer: Match the opening paragraph and major headings with the search question and the visitor's decision. Evidence of completion: A reader can state the answer and next action from the first screen.
- 4. Trace navigation: Follow links from the homepage or topic hub to the selected pages and inspect their anchor text. Evidence of completion: Each important page has a contextual incoming link and no broken next step.
- 5. Rank fixes: Score each finding by impact, confidence, and effort, then select the three highest-confidence actions. Evidence of completion: The list names an owner, expected output, and retest method for each fix.
A worked example
A new SaaS homepage returns 200 and appears in the sitemap, but its canonical uses a preview hostname. The features page has a descriptive title but no link from the main navigation, and the blog article opens with a broad industry introduction instead of answering its title question. The audit ranks the canonical fix first, the navigation link second, and the article opening third. The team can verify each change with a raw fetch, a short crawl, and a page read rather than waiting for a composite audit score to move. Treat the example as a model of the reasoning, not as a universal benchmark. The useful part is the chain from question to evidence to action. Preserve the exact entity names, scope, and conditions that a reader would need if an answer engine quoted the passage outside the page. If a number comes from a report, state the reporting window. If a result comes from a test, state the URL type, device or crawler, and date. A compact example earns its space when it helps the reader make the same decision on another page. Remove invented precision, anonymous authority, and conclusions that reach beyond the recorded evidence.
- One conflicting canonical outranks several cosmetic metadata edits.
- A crawl path confirms both discovery and the page's place in the site.
- A direct answer gives searchers and answer systems a usable passage.
Avoid the mistakes that weaken the result
Short audits fail when the reviewer tries to cover the entire site, trusts a score without evidence, or mixes confirmed defects with optional improvements. Keep the sample small and state what each check proves. Fix the first mistake that changes eligibility or meaning before editing smaller presentation details. Keep source boundaries visible: one citation should support the nearby claim, while a separate claim should receive its own source. Do not repeat the target phrase to manufacture relevance. Search systems can use titles, headings, visible text, links, structured data, and other signals, so those elements should agree on the subject without copying one sentence across the page. Check the public result after deployment because a correct content record can still produce the wrong page through caching, layout inheritance, JavaScript failure, or a stale build.
- Auditing fifty URLs with no representative page types creates noise. Correction: Sample the templates that carry the main search and business jobs.
- Treating every warning as equal hides the blocker. Correction: Rank access and identity faults before copy polish.
- Changing several fields at once destroys attribution. Correction: Ship a small batch with a dated before-and-after record.
Verify the result and choose the next action
Retest the three selected URLs after deployment. Require the intended response, canonical, visible title, H1, answer, and internal link in the production output. Then watch indexing state and representative query impressions over a stable period. Use a fixed observation window and compare like with like. Record the query set, country, device, page version, and publication or change date. Search impressions can show discovery and query matching; clicks and useful sessions show whether the result attracted the intended reader. Observed AI citations add a separate retrieval signal, but a citation count does not prove traffic or revenue. Review the cited passage when you can and check whether the answer preserved its subject, scope, conditions, and source. Keep the page stable long enough to collect evidence unless you find a factual error, broken route, security problem, or misleading claim. The next edit should respond to the strongest observed failure instead of a generic scoring recommendation.
- Save a before-and-after crawl record for the same URLs.
- Confirm that Search Console inspects the expected canonical where access exists.
- Review qualified visits and conversions separately from technical pass rates.
Put it to work
Find the highest-impact fix on your site.
Capture crawl, canonical, metadata, content, and link evidence for an important public URL.
Run the 30-minute auditSources
- 1.Google Search Central: In-depth guide to how Google Search worksChecked 2026-07-26
- 2.Google Search Central: SEO Starter GuideChecked 2026-07-26
- 3.Google Search Central: Creating helpful, reliable, people-first contentChecked 2026-07-26