GSC Fixer — User Guide
How to diagnose, fix, and monitor your Google Search Console health — step by step.
How to diagnose, fix, and monitor your Google Search Console health — step by step.
Get from install to fixed in under 10 minutes.
gscf_data, gscf_findings, gscf_fixes, gscf_baselines, gscf_snapshots).| Step | Where | What happens |
|---|---|---|
| Connect Google Search Console | Settings page | OAuth flow with Google. Plugin stores a refresh token locally. |
| Select property | Settings page | Match the Google Search Console property to this site (e.g. https://yoursite.com/). |
| Run Scan | Dashboard | 12 diagnostic checks run against your database and live site. Findings appear with severity colors: 🔴 critical, 🟡 warning, 🔵 info. |
Each finding shows: severity, a plain-English description, how many pages are affected, and sample URLs. The common findings and what they mean:
| Finding | Severity | What it means | What the fix does |
|---|---|---|---|
| Pages have is_public = NULL | 🔴 Critical | These pages are silently excluded from your sitemap — Google never sees them. | Sets the flag so pages enter the sitemap. Resubmit sitemap after this one. |
| Ambiguous noindex state (NULL) | 🟡 Warning | Yoast hasn't decided — Google may or may not index these pages. | Sets explicit "indexable" state. |
| No canonical URL | 🟡 Warning | Google guesses the canonical, sometimes wrong → duplicate content flags. | Adds self-referencing canonicals. |
| Stale canonicals | 🟡 Warning | Canonical points to an old/removed URL. | Rewrites canonical to the current permalink. |
| Missing SEO title / meta description | 🟡 Warning | Google writes its own title, usually worse CTR than a hand-written one. | Not auto-fixed — needs content work (PRO flags it, you write the metas). |
| Sitemap noindex header | 🔴 Critical | Your sitemap itself is marked "noindex" — Google ignores the whole sitemap. | Output-buffer fix that strips the header, survives SEO plugin updates. |
| Schema gaps | 🔵 Info | Missing JSON-LD structured data (WebSite, Organization). | Guidance — usually needs theme/plugin work. |
yoursite.com/sitemap_index.xml in your browser — the URL count should have grown (if is_public was fixed).The complete lifecycle from install to healthy site:
The rule: resubmit whenever your sitemap's contents changed in a way Google should know about immediately. GSC Fixer handles this automatically in most cases — here's the full picture:
| Situation | Why |
|---|---|
| You used Fix All | Fix All resubmits the sitemap automatically after database fixes (when Google Search Console is connected). |
| Publishing a new post/page | Yoast updates the sitemap; Google picks it up on its normal crawl. The IndexNow integration (PRO) also pushes the new URL to Bing/Yandex/DuckDuckGo instantly. |
| Updating existing content | Same — lastmod changes, Google recrawls on schedule. |
| Situation | How |
|---|---|
| You applied individual fixes (not Fix All) that affect sitemap contents — is_public fix, canonical fixes, sitemap noindex header fix | GSC Fixer → Settings → Resubmit Sitemap (or re-run Fix All, which does it for you) |
| First-time connecting the plugin to a site with existing Google Search Console issues | Settings → Resubmit Sitemap after your first fix round |
| You migrated/changed URL structure | Settings → Resubmit Sitemap after fixing canonicals |
| Google shows "Sitemap could not be read" or "0 discovered pages" in Google Search Console | Fix the underlying issue first (scan will tell you), then resubmit |
Fixes apply to your database instantly, but Google's reactions take time. Here's what to expect and when to check:
| Layer | What it covers | How to use |
|---|---|---|
| 1. Pre-fix backup | The plugin's own tables (findings, fixes, baselines, data, snapshots) | Automatic on first fix — downloads before any change |
| 2. Scoped rollback SQL | The exact rows each fix changed — captured at fix time | Fix History → Revert button. Restores only what that fix touched, nothing else. |
| 3. Your own full DB backup | Everything | Recommended before your first fix round (host backup or a backup plugin) |
Revert is safe: it restores the exact previous state of only the rows that fix changed — verified behavior: fix → revert → re-apply produces identical results.
A: The fixes are in metadata Google reads — canonical tags, indexable flags, sitemap contents. Nothing visible changes for human visitors. To verify: check your sitemap URL count, view-source a page for the canonical tag, and watch Google Search Console over the following days. The dashboard's health score and findings list are your in-plugin verification.
A: No. Titles and descriptions are content decisions, not mechanical fixes. GSC Fixer flags them; you (or your SEO workflow) write them. Everything else — flags, canonicals, headers — is auto-fixed.
A: Daily (configurable in Settings). You'll get an email alert only when something changes for the worse, and a weekly summary report. Silence means healthy.
A: Yes — Rank Math, AIOSEO, SEOPress, and The SEO Framework are detected. Most database-level fixes target the Yoast indexable table; other plugins' equivalents are on the roadmap.
A: GSC tells you what Google observed (lagged by days/weeks). GSC Fixer's scan tells you what's technically wrong right now in your database — and fixes it immediately. Use both: fix now with the plugin, measure results in GSC.
A: No. New or low-traffic sites genuinely have near-zero Google Search Console data. Click "Refresh GSC Data" (the button name) after 24–48h post-fix to pull fresh numbers. Indexing growth is a weeks-scale curve, not instant.