How to Audit Your Website's SEO With AI in One Afternoon

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Audit Your Website's SEO With AI in One Afternoon.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Audit Your Website's SEO With AI in One Afternoon.

Run an AI SEO audit in one afternoon by limiting it to your most important pages, collecting evidence from Google Search Console and your website, then asking AI to organise the findings. Spend four hours checking search access, page clarity and customer actions, and finish with a short repair list rather than an unexplained score.

This is a focused review for a small business website. It will not certify a large site or reveal every technical fault. AI is useful for comparing text and sorting evidence, but a confident diagnosis is not proof that it visited your pages or tested their settings.

Follow me on Instagram@sagnikteaches

Reserve four hours and choose six pages

SEO means helping search engines understand your website and helping suitable customers find it. For an afternoon audit, choose the home page, two important service pages, a page answering a common buying question, the contact page and the booking or enquiry destination.

Connect on LinkedInSagnik Bhattacharya

Before the session, confirm that you can view the website and access its Search Console property. A property is the website or website section represented in that account. If access is missing, ask the current owner to arrange it. You can still review public pages, but mark search-data checks as incomplete.

Subscribe on YouTube@codingliquids

Use a spreadsheet with columns for page, observation, evidence, likely customer effect, proposed fix, owner and verification. Keep one finding per row. Save screenshots or report dates where helpful, but leave customer data and login details out of any AI input.

TimeCheckRequired output
First 15 minutesScope and baselineSix pages and a record of what success means
Next 30 minutesSearch performancePages and queries worth investigating
Next 40 minutesIndexing and accessEvidence for any missing priority page
Next 45 minutesContent, titles and linksSpecific gaps and inaccurate promises
Next 30 minutesPhone experience and speedObserved customer obstacles
Next 30 minutesAI-assisted triageFindings separated from hypotheses
Next 35 minutesSmall fixes and retestsEvidence that completed repairs work
Final 15 minutesHandoverOwners, due dates and the next review date

Do not spend the whole afternoon improving a score on the home page while a service enquiry form is broken. The timetable is a limit on investigation. When an issue needs specialist work, record a clear task and continue.

Use search data to choose what deserves attention

Open the Search Console Performance report. It provides clicks, impressions, click-through rate and average position, with views such as Pages and Queries. An impression records an appearance in search; click-through rate is clicks divided by impressions. These measures describe search activity, not completed sales.

Choose a recent complete period and a sensible comparison. For example, compare two 28-day periods while recording seasonal changes, advertising and closures. A low-volume business may need a longer period. Keep the dates and report filters attached to any exported numbers.

  • Check important pages first. Identify which of your six pages receive impressions and clicks.
  • Read the queries behind a page. Do they describe a service you provide?
  • Look at meaningful changes. Distinguish a genuine pattern from a movement of one or two clicks.
  • Record uncertainty. Missing or limited data is a reason to investigate, not a diagnosis.

Illustrative example: a guest house page receives 900 impressions and 18 clicks in one period. Its click-through rate is 2%. The next period has 1,000 impressions and 15 clicks, or 1.5%. That alone does not prove the title is poor. The mix of queries or search positions may have changed.

Search Console now has a second place to look. Google's Search Generative AI performance reports, available to all websites since 31 August 2026, show how often your pages appeared in AI Overviews and AI Mode, broken down by page and date. Note which of your six pages appear there. The launch post lists impressions only, not clicks, and the same impressions are already counted in the main Performance report, so don't add the two together.

Inspect the page and queries before rewriting anything. If the page is appearing for breakfast-only enquiries but breakfast is available only to staying guests, clearer wording may improve the fit even if it reduces irrelevant clicks.

Establish whether priority pages can be found and indexed

Indexing means a search engine has included a page in its searchable collection. In Search Console, enter a priority page's full address in URL Inspection. Review the indexed result, then use Test live URL when you need to inspect the current page. The two views can differ.

Google says a successful live test does not guarantee indexing. It also says the Google-selected canonical, its chosen representative address for duplicate versions, is determined in indexed data rather than predicted by the live test. Use Google's URL Inspection documentation if you need help interpreting the result.

For each important page, check whether it opens without a customer login and whether there is a normal link to it from another useful page. Ask your website helper to investigate any unexplained access or indexing warning. Copy the exact reported issue into the task rather than asking AI to guess.

Two controls are often confused. A robots.txt rule can restrict crawling, while a noindex instruction tells a search engine not to index a page. Do not remove either across the whole website because one public page is missing. Private account pages may have deliberate restrictions.

Illustrative maintenance-firm mistake: the public gutter-clearing page still has a noindex instruction left from a redesign. AI proposes “publish more supporting content”. The observed instruction is the first issue to investigate. Have the website owner confirm it is accidental, remove it from that page and test again.

Not every excluded address is a problem. Duplicate versions, old redirects and private pages may be intentionally absent. Judge exclusions against your list of public pages that customers should find, rather than trying to make every reported address indexed.

Read the six pages as a customer with a specific task

Check the page title, main heading, opening text and next action together. Can you tell what is being offered, who it suits and how to enquire? A home page saying “Welcome to excellence” gives less help than a direct explanation of the service.

Google's SEO Starter Guide recommends clear, concise titles that accurately describe each page. It explains that search titles can draw on several page elements, and snippets can come from page content or a meta description. Writing a description does not guarantee Google will display it unchanged.

  • Check purpose: each page should answer a recognisable customer need.
  • Check claims: prices, availability, qualifications and restrictions need an approved source.
  • Check headings: use them to organise real questions and sections.
  • Check links: open the important service, enquiry and booking links.
  • Check repeated text: ask whether similar pages serve different needs before combining them.

Illustrative letting agency before: the page title is “Services”, and the opening says “We provide comprehensive solutions for every owner.” After review, the proposed title is “Property management and tenant-finding services”. The opening explains those two services and links to their actual scope.

Do not add “guaranteed rental income” because AI thinks it sounds persuasive. If the business offers no such guarantee, it is a factual failure. Use the website copy tutorial when the evidence points to a substantial rewrite.

A second illustrative issue is less visible: a tour operator's preparation page says “book this departure”, but its button opens an expired event. Replace the destination with the correct live route, then test it. This is a specific repair with an observable result.

Test the phone journey and interpret speed reports carefully

Open the website on a phone and perform the task a customer would attempt. Read the service, find the restrictions, open the enquiry form and submit a clearly labelled test if you can do so safely. Warn the receiving team, then remove the test record through the normal process.

Look for practical obstacles: text covered by a banner, a button that is hard to tap, a form that rejects valid input or a confirmation that never reaches the team. Record the device, page and steps. These are customer-journey checks alongside the SEO audit, not claims that every obstacle is a ranking factor.

Use PageSpeed Insights on a priority page. It distinguishes laboratory tests, which simulate a visit, from field data drawn from real use. The field view covers a trailing 28-day period. Where data is unavailable, do not invent a real-user result from the laboratory score.

Illustrative campsite finding: the booking page's main image appears to delay useful content in a test. Ask the website helper to inspect the image and the report's diagnostics. Do not tell them to remove all photographs. They need to confirm the cause and preserve the information customers need.

After a change, rerun a comparable laboratory test and check the page manually. Historical field data will not instantly describe the revised page. A green score is also not proof that the booking journey works.

If visitors arrive but fail to enquire, use the website conversion diagnosis tutorial for a deeper review. Keep evidence of search visibility separate from evidence of usability.

Ask AI to organise evidence without inventing an audit

Give AI your observations and selected public page text. Label each source. Do not write “audit my whole website” and assume the assistant crawled every page. The safest output is a short table of supported findings, possible explanations and checks still needed.

Organise these website audit notes. Use only supplied evidence.
Do not claim you visited pages or ran technical tests.
For each finding return: evidence, customer effect, confidence,
proposed action, owner needed, and how to verify the repair.
Separate confirmed observations from hypotheses.

A1: service page opens; its enquiry button leads to a missing page.
A2: Search Console reports noindex on a public service page.
A3: home-page text says emergency repairs; owner confirms planned work only.
A4: fewer clicks this month; no query comparison collected yet.
Do not infer causes for A4.

Illustrative output: “A1: confirmed broken enquiry route; repair destination and complete a test enquiry. A2: investigate whether noindex is intentional; website owner required. A3: correct the unsupported emergency claim. A4: insufficient evidence; compare queries and dates before recommending a fix.”

If the output says “A4 proves an algorithm penalty”, strike that out. Nothing in the notes supports it. Keep the useful organisation and reject the diagnosis. AI should not turn a gap in your evidence into a confident technical explanation.

Use three priority groups: blocks customers or search access; misleads or confuses customers; could improve presentation. These are working priorities, not an industry scoring standard. Within each group, choose the change with the clearest evidence and a practical verification step.

A letting agency leaves with three repairs, not 40 warnings

In this illustrative audit, a four-person letting agency has 18 public pages and reviews six. It spends the four-hour allowance on inspection and small repairs. At an assumed internal time value of $30 an hour, the audit uses $120 of staff time. Any developer work or new subscription is extra and should be priced separately.

The audit finds a broken appraisal button, an old emergency-contact promise and an unexplained indexing issue on the management page. It also finds inconsistent punctuation and several vague headings. The owner puts the first three into the immediate repair plan.

FindingAction and ownerProof of completion
Appraisal button opens a missing pageWebsite editor corrects the destinationA labelled test enquiry reaches the agency
Page promises emergency cover that is not offeredLettings manager approves corrected wordingPublished page matches the current service terms
Management page has unexplained indexing statusWebsite supplier investigates the recorded reportCause documented; any repair tested and later indexing checked

The owner does not mark the third item fixed merely because an indexing request was submitted. The record stays open until the cause and outcome are understood. Punctuation changes wait because they do not block the current enquiry route.

For small edits you can safely make, keep the old wording or destination, publish the approved change and retest. Do not use the afternoon to experiment with site-wide redirects, templates or crawler settings without a responsible website maintainer.

If the site has hundreds of pages, repeated technical faults or unexplained traffic losses, this sample can help brief a specialist. Use the SEO agency selection tutorial to ask for an investigation grounded in the evidence you collected.

Handle missing data without turning guesses into findings

A new guest house website may have too little search history for a useful comparison. In that illustrative case, record the date measurement began and focus on observable checks: whether the rooms page explains the options, whether the booking link works and whether important public pages can be inspected. Do not fill an empty report with AI-generated estimates of traffic.

Use a simple evidence label beside every finding: observed directly, reported by a tool, confirmed by the owner or still untested. A claim can need more than one label. “Customers cannot book on a phone” should be reproduced on the stated device before it becomes a confirmed fault; one vague complaint is a lead for investigation.

For example, a guest house owner receives a message saying that a room cannot be booked. Your test succeeds. Ask which dates and room type were selected, without requesting payment details. The problem may concern sold-out dates, a particular room or an unclear availability message. Record what you tested instead of closing the issue as imaginary.

Similarly, if an assistant says the site has duplicate content, ask for the two page addresses and the passages it compared. Read them side by side. Two rooms may legitimately share arrival information while differing in capacity and facilities. Preserve those useful distinctions; do not delete a room page simply because repeated text triggered a generic recommendation.

These checks keep the repair list honest. A smaller list with reproducible evidence is easier to price, delegate and verify than a long list of alarming guesses.

Close the afternoon with a dated verification list

Give every unfinished item an owner, a due date and a check. “Improve SEO” is not a task. “Confirm why the management page is excluded, document the cause and retest any repair” is.

Check functional fixes as soon as they are published. Review search results over a later comparable period, allowing for recrawling, low traffic and seasonal differences. Keep the same report filters and record other changes so the comparison remains intelligible.

Your finished audit should contain the six-page scope, a small set of supported findings, completed tests and a ranked repair list. It should also say what was not checked. That gives the business a usable plan and gives the next person enough evidence to continue without repeating the whole afternoon.

Further reads

Sources: Google Search Console URL Inspection, Page indexing, Performance report and page-availability documentation; Google Search Central SEO Starter Guide; Google PageSpeed Insights documentation; Google Search Central announcement of Search Generative AI performance reports. Checked 28 September 2026.

Turn your SEO findings into a manageable repair plan

On a 1:1 call, we can review your evidence, separate content fixes from technical work and choose the changes most relevant to your enquiry and booking process.

Book a 1:1 call with me