PlugsightDocs

Run an SEO health check

Check a site's organic search health with your AI - traffic trends, quick-win queries, indexing, sitemaps and page speed - and get a fix list.

This guide runs a complete SEO health check on one site: how organic traffic is trending, which queries are close to paying off, whether Google can index the important pages, and how fast they load. You finish with a prioritised fix list.

Plugsight only reads. It can't change your site, submit sitemaps or request indexing; your AI tells you what to change.

What you need

  • A Pro or Agency plan, for Search Console.
  • A Google Search Console connection that reaches the site, in your MCP server.
  • Optional: a Google Analytics 4 connection for the same site, to see what organic visitors do.
  • Page speed checks need nothing: PageSpeed Insights works on every plan and every server.

Step 1: pick the site

  1. Start a new chat with the right MCP server switched on.
  2. Ask "List my Search Console sites."
  3. Name the site in every question, for example "for https://www.example.com/" or "for the example.com domain property".

Step 2: the traffic trend

  • "Compare organic clicks, impressions, CTR and average position for this site, last 28 days against the 28 days before."
  • "Which pages lost the most clicks compared with the previous period?"

Search Console data becomes final about 2–3 days after each date, and Plugsight includes the fresh, not-yet-final days by default. If the latest days look low, ask again for a range that ends 3 days ago. See Get accurate numbers from marketing data.

Step 3: quick wins

  • "Run an SEO opportunities report for this site."

The SEO opportunities deep dive returns:

  • Queries close to page one (worth a content refresh or more internal links).
  • Page-one results with low CTR for their position (worth a better title and description).
  • Pages losing clicks.

It only looks at queries with at least 100 impressions, unless you ask for a different threshold.

Step 4: indexing

For the pages that matter most (home page, top products or services, pages that lost clicks):

This uses URL inspection: whether the page is indexed, when Google last crawled it, the canonical Google chose, mobile usability and rich results. Ask about one page at a time.

Then check the sitemaps:

  • "Which sitemaps are submitted for this site? How many URLs are submitted and indexed, and are there errors or warnings?"

Step 5: page speed

  • "Check the speed of https://www.example.com/ on mobile. Does it pass Core Web Vitals, and what are the three biggest fixes?"
  • "Check the same page on desktop."

Each check takes 10 to 40 seconds. Real-user Core Web Vitals need enough Chrome visits; for a quiet page your AI is told there isn't enough data, and the lab scores still work.

Step 6: what organic visitors do (needs GA4)

  • "In GA4, how many sessions, key events and how much revenue came from organic search last month compared with the month before?"
  • "Which landing pages from organic search have the lowest engagement rate?"

Step 7: the fix list

  • "Summarise the health check as a table: issue, page or query, evidence, and the fix. Put indexing problems first, then speed, then content opportunities."

Run it regularly

A monthly check catches problems early. Ask the same questions each time, with the same date ranges, so you can compare. A shorter version for busy months: Steps 2, 3 and the sitemap question in Step 4.