Search Console Audit, Pass Four: A New Row and Three We're Watching

By Rakshit Yadav (@yadavrakshit60)•Oct 2026•7 min read

Short answer: This is the fourth pull of our own Search Console Performance report, and three of the four rows are pages we'd already touched in the first pass and the third pass — /skills (48 impressions, 0 clicks, position 66.7 on "cursor skills"), /commands (6 impressions, 0 clicks, position 13.7 on "cursor slash commands"), and /tools/config-converter (4 impressions, 0 clicks, position 88.3 on "config maker"). The fourth row is new: /compare/cursor-rules-vs-skills is sitting at 13 impressions, 0 clicks, position 29.1 for "cursor rules skills docs" — a near-miss on a query that explicitly wants a documentation-grounded answer, not an opinion piece. Below is what Search Console showed for each row, and the one fix we shipped for the new row plus confirmation checks on the three repeat rows.

Repeat rows showing up in a later pull isn't a failure of the earlier fixes — Search Console's Performance data lags, and position at single-digit impression counts is noisy. The honest read is: we can't yet tell whether the round-three fixes to /skills, /commands, and /tools/config-converter moved anything, because this pull is too close to when those fixes shipped to show it. What we can act on immediately is the new row, /compare/cursor-rules-vs-skills, and that's where this pass's actual change lives.

The four rows, as pulled this time

PageQueryImpressionsPositionCTRStatus
/skillscursor skills4866.70%Fixed in pass three; too soon to confirm movement
/compare/cursor-rules-vs-skillscursor rules skills docs1329.10%New row — fixed this pass
/commandscursor slash commands613.70%Fixed in pass three; too soon to confirm movement
/tools/config-converterconfig maker488.30%Fixed in pass three; too soon to confirm movement

The new row: /compare/cursor-rules-vs-skills at position 29.1 for a docs-seeking query

Position 29.1 on 13 impressions is the same shape of near-miss we flagged in the first pass: Google already trusts the page enough to show it on page 3, and the content underneath (a rules-vs-skills-vs-commands comparison table, already live near the top of the page) is the right shape for the query. What wasn't right was the framing. The query is "cursor rules skills docs" — the word "docs" is a strong signal that the searcher wants a grounded explainer tied to Cursor's own documentation, not a branded opinion piece. The page's title tag and H1 read "Cursor Rules vs Skills vs Commands," which is accurate but doesn't signal "this is the official-docs answer" the way the query implies.

The fix: we rewrote the meta title and H1 to lead with "Cursor Rules vs Skills: Official Docs Explained," and tightened the lede paragraph to open by attributing the rules/skills/commands split directly to Cursor's own documentation before restating it in plain language, with the existing link to Cursor's docs on commands kept in the first comparison section rather than buried further down. We did not change the comparison table itself — it was already correct — because the gap here was framing and intent-matching, not missing content.

Why we're not claiming the three repeat rows are still broken

/skills, /commands, and /tools/config-converter all got concrete fixes in the third pass: a Cursor-first title and intro for /skills, a dedicated "Cursor slash commands" section for /commands, and a "config maker" synonym pass for /tools/config-converter. Seeing the same impressions-with-zero-clicks pattern in this pull doesn't mean those fixes failed — Search Console's Performance report has a reporting lag of a few days, and at single-digit-to-low-double-digit impression counts, position and CTR are both noisy from week to week. The honest thing to do with this data is wait and re-check in 2-3 weeks, which is exactly the rule from the checklist in the first pass. We verified each page still carries its round-three fix (the Cursor-first title on /skills and /commands, the "config maker" phrasing on /tools/config-converter) and left the content alone rather than re-editing something that may just need more time to show up in the data.

The rule this pass reinforces

A query containing "docs" is its own signal, distinct from "position stuck in the 60s" or "0% CTR on a branded term." It means the searcher has already decided they want a reference answer, usually because they're debugging a disagreement between two tools or deciding which mechanism to use, and they expect the top result to either be the vendor's own documentation or a page that visibly draws from it. For that query shape, the fix isn't a longer comparison — the table on /compare/cursor-rules-vs-skills was already correct before this pass — it's making the title and opening paragraph say "this is grounded in the official docs" instead of making the reader infer that from a citation three sections down.

A checklist for a "docs"-flavored query specifically

  1. Does the query contain "docs," "documentation," "official," or a specific vendor name alongside a feature term? That's a reference-intent signal, not a general-interest one.
  2. Does your title tag or H1 promise a reference answer, or does it read like a blog headline? If the query says "docs" and your title doesn't echo that intent, rewrite the title first.
  3. Is the citation to the vendor's actual documentation in the first section, with a real link, or is it buried in a "sources" list at the bottom? Move it up if the query is doc-seeking.
  4. Don't touch the content underneath if it's already structurally correct (a table, a direct comparison) — the gap at position 20-40 for this query shape is almost always framing, confirmed again in this pass after confirming it the first time on /compare/cursor-rules-vs-skills itself when it showed up at a very similar position (29.1) in two separate pulls.

What we actually changed on /compare/cursor-rules-vs-skills

Three concrete edits, all in the page's title/framing layer, none in the comparison table itself:

  1. Meta title: from "Cursor Rules vs Skills vs Commands: Differences Explained (2026)" to "Cursor Rules vs Skills: Official Docs Explained (2026)" — leading with "Official Docs" because that's the exact intent signal in the query ("cursor rules skills docs"), not a guess at a better-sounding headline.
  2. H1: matched to the new title, so the SERP snippet and the on-page heading agree the moment someone lands — a mismatch there is its own small trust signal loss, independent of the title-tag fix itself.
  3. Lede paragraph: rewritten to open with "Per Cursor's own documentation..." and attribute the rules/skills/commands split to the vendor's docs before restating it in plain language, with the existing link to Cursor's docs on commands kept in the first section rather than in a sources list at the bottom.

What we deliberately left alone: the comparison table, the "use a rule when" / "use a skill when" sections, and the FAQ block. All three were already structurally correct for a comparison query — the gap was entirely in whether the title and opening line told a doc-seeking searcher "yes, this is grounded in the vendor's documentation" before they had to scroll to find out.

Why this matters more than it looks like it should

It's tempting to treat a three-word change to a meta title as too small to matter, especially next to 13 impressions. But position 29.1 means Google has already decided the page is relevant enough to show on page 3 for this exact query — the ranking work is effectively done. What's left is purely a matching problem between what the searcher typed and what the snippet promises, and that's the cheapest kind of SEO lift available: no new content, no new backlinks, just making the existing page say back to the searcher the thing they already told Google they wanted. That's the same logic from the original audit's core claim — a page with impressions and no clicks, or a near-miss position, is a relevance problem, not a ranking problem, and relevance problems are fixed at the title and lede, not by writing more.

FAQ

Why does the same page show the same Search Console numbers across two audit passes? Search Console's Performance report lags real-time by a few days, and position/CTR at low impression counts (under ~50) are noisy week to week. Seeing the same row again doesn't mean a prior fix failed — it means there hasn't been enough time or volume to tell yet.

What does a query containing the word "docs" actually signal? It signals the searcher wants a reference-grounded answer — ideally one that cites or visibly draws from the vendor's own documentation — rather than a narrative opinion piece. The fix is usually a title and framing change, not new content, if the page already has the right structural answer (like a comparison table).

Should I re-fix a page every time it shows up again in a later Search Console pull? No. Re-editing a page before giving a prior fix 2-3 weeks to show up in the data just adds churn without a signal to act on. Confirm the fix is still live, then wait.

Is /compare/cursor-rules-vs-skills at position 29.1 a ranking problem or a framing problem? Framing. Position 29 on a query that explicitly says "docs" means Google already trusts the page enough to surface it on page 3 — the comparison table underneath was already the right content. The fix was rewriting the title and H1 to match the doc-seeking intent, not adding content.

Sources

A fifth pull caught two new shapes of the same problem: a page-1 listing stuck at 0% CTR, and /commands quietly splitting its ranking across two related queries — see pass five for the fix on each.

Written by Rakshit Yadav. Published 2026-10-30, last updated 2026-10-31.

Related Tools & Agents

🛠️ Free Tool: config-converter🤖 Agent: seo-specialist⚡ Command: /seo-auditSkill: on-page-seo

Run this checklist automatically

The on-page SEO skill and /seo-audit command apply this exact method to any page you point at.

See the on-page SEO skill →