The system knows what is indexing, ranking, and where authority is moving.
Google Search Console connects via OAuth in the onboarding session. From that point, IGNY8 syncs hourly — and the data feeds directly into the pipeline.
Four streams of search intelligence.
Connected once via OAuth, then synced every hour without the operator triggering anything.
Search performance
Impressions, clicks, and average position per query and page.
Indexation status
Which URLs are indexed, and which are not.
URL inspection
Inspection results pulled in for every tracked URL.
Core Web Vitals
Performance signals synced alongside everything else.
GSC data feeds directly into the pipeline.
It is not a dashboard you check. It is infrastructure other parts of the system run on.
Content refresh sweep
Search performance identifies pieces that have drifted.
Backlink KPI snapshots
External link impact measured against real ranking movement.
Site cockpit
Search performance shown alongside pipeline activity.
Not a one-time pull. A standing connection.
The system monitors search performance the way it monitors everything else — automatically, hourly, without the operator triggering a sync.
| Aspect | Detail |
|---|---|
| Connection | OAuth, set up during onboarding |
| Sync frequency | Hourly, automatic |
| Operator action | None — no manual sync required |
| Role | Infrastructure, not a report |
- Search performance per query and pageHourly
- Indexation statusHourly
- URL inspection resultsHourly
- Core Web VitalsHourly
Data checked occasionally
A manual export is a snapshot — stale the moment it is taken, disconnected from everything else.
- Manual export, when someone remembers
- Stale the moment it is taken
- Disconnected from the pipeline
- No link between what was built and what ranks
Data the system runs on
Hourly sync means the pipeline always works from what is actually ranking right now.
Hourly sync. Four data streams. Zero manual triggers.
Where search data usually goes stale.
Search performance the system cannot see is search performance the system cannot act on.
| Anti-pattern | Why it fails | The IGNY8 approach |
|---|---|---|
| Manual GSC exports | Stale, occasional, easy to forget | OAuth connection with hourly automatic sync |
| Search data in a separate tab | Never connects to what the pipeline does | GSC data feeds the refresh sweep and KPI snapshots |
| Guessing which content has drifted | Decay is found late, after rankings drop | Search performance identifies drift continuously |
| No view of built vs ranking | No way to prove the work compounded | Site cockpit shows search performance beside pipeline activity |
Connect once, then it runs itself.
From a single OAuth connection to a continuous feed the rest of the system depends on.
- 01Connect via OAuthGoogle Search Console linked during the onboarding session.
- 02Sync hourlyPerformance, indexation, inspection, and Web Vitals pulled in.
- 03Feed the pipelineData routes into the refresh sweep and backlink KPI snapshots.
- 04Show in the cockpitSearch performance displayed alongside pipeline activity.
See what is ranking, hourly.
Connect a URL, link Search Console, and the pipeline runs on live search data.