There are two search engines now. Most sites are invisible to the second one.
Google still sends traffic. But ChatGPT, Perplexity, Claude and AI Overviews now answer the question before anyone clicks — and they can only cite sites they are allowed to read and able to parse. SEO Autopilot fixes both layers, then keeps publishing into them. Every month. Measured on a scorecard that never moves the goalposts.
The failures are structural, not cosmetic.
Across every site we have audited, the same handful of problems account for most of the missing visibility — and none of them are "write better content" problems. They are configuration problems, which is exactly why a system can fix them.
Your firewall is blocking the AI crawlers
One client's WAF returned 403 to ChatGPT's and Claude's crawlers while their own monitoring tool reported "all 16 AI crawlers accessible." The tool checked cheaply. We fetched and parsed. The tool was wrong.
There is no structured data at all
No JSON-LD means no rich results, no entity graph, and nothing for an answer engine to lift a fact from with attribution.
No llms.txt, no crawl guidance
The file that tells AI systems what your site is and which pages matter simply does not exist on most sites.
Your template is quietly breaking every page
On one site, 30 of 39 pages had zero H1 — because the post template used an H2 for the title. One widget change fixed 21 pages at once and made every future post correct by default.
Seven days from access to a measured, running system.
Month one is the proof sprint. You give us access on day zero. By day seven the foundation is measurably repaired, the plugin is live, the content engine is publishing, and you have a before-and-after scorecard in your hands. Then you decide whether month two happens.
Access handshake
Search Console and Analytics access granted to the Aglocom service account named in your kickoff email, a WordPress application password issued, and the plugin installed. Roughly twenty minutes of your time. This is the only thing we need from you all week.
Baseline audit — and the scores get frozen
Every URL in your sitemap is fetched and parsed live. Not a tool export — an actual crawl. You get two scores on a fixed rubric, plus a gap register where every finding is ranked by severity and labelled either we fix this or this needs a decision from you. The baseline is frozen. Every later number is measured against it.
The plugin does the mechanical repairs
Titles and meta descriptions, Open Graph, JSON-LD schema across page types, breadcrumbs, canonical hygiene, sitemap cleanup, thin taxonomy pages de-indexed, security headers, XML-RPC closed. Work that would take a developer a fortnight, applied as configuration.
The AI layer gets opened
AI crawler access verified crawler-by-crawler against your firewall and robots rules, llms.txt published, IndexNow wired, and the answer-engine schema layer switched on. This is the half of search that most agencies still do not measure.
Demand research and the 90-day calendar
Live search volume, your competitors' ranking keywords, and your own Search Console demand — including the queries you already get impressions for and lose. Out of it comes a content pillar map and a dated 90-day calendar, each post assigned one job so your pages never compete with each other.
First posts live, and the re-score
The first articles publish in your site's own design language, under your author byline, with internal links and schema already attached. Then we re-run the audit and hand you the delta. Day seven ends with a report, a live dashboard, and a queue that keeps publishing whether or not anyone logs in.
What seven days cannot do — and we will not pretend otherwise
New pages take roughly two to four weeks to show up in Search Console at all, and competitive positions move over months, not days. Anyone promising you rankings in a week is either guessing or lying. What week one buys you is the foundation and the engine: the structural problems fixed, the crawlers let in, and content shipping on a schedule. Ranking movement is what months two and three are for, and we report it against a baseline we froze before we touched anything.
Two scores. Fixed weights. Never re-cut mid-engagement.
Most agency reporting is unfalsifiable because the measure changes with the result. We learned this the hard way: on an early engagement the rubric changed between the first and second audit, so the headline number spanned a rubric change rather than real work. The two audits were never comparable.
So the rubric is now versioned and frozen at your baseline. Categories are never added, dropped or re-weighted during an engagement. If a new concern appears, it gets scored inside an existing category. Both scores are published every month, with weight, raw score, weighted contribution and the delta against the prior audit. Never one score without the other.
Every number is measured by fetching your live pages — never read off a third-party dashboard. Where a tracker and our crawl disagree, the crawl is the score of record and the audit explains why.
| Score A — SEO Health | |
|---|---|
| Technical SEO | 25% |
| Content quality & E-E-A-T | 25% |
| On-page SEO | 20% |
| Schema / structured data | 10% |
| Performance (Core Web Vitals) | 10% |
| Images | 5% |
| Internal linking & architecture | 5% |
| Score B — AI Visibility (AEO / GEO) | |
|---|---|
| AI schema & structured data | 25% |
| AI crawler access | 20% |
| llms.txt | 15% |
| AI content readability | 15% |
| AI content gap | 15% |
| AI review signals | 10% |
What the scorecard looked like on a real engagement.
A US healthcare analytics company, WordPress behind a firewall. Baseline frozen 15 July 2026, re-measured 18–19 August 2026 by fetching all 39 sitemap URLs live.
AI Visibility nearly quadrupled because three structural zeros were closed: a firewall that returned 403 to ChatGPT's and Claude's crawlers, the total absence of JSON-LD, and a missing llms.txt. Those three carry 60% of the AI score between them.
One category went backwards, and we published that too
Performance fell from 48 to 28. Removing the firewall to let the AI crawlers in also removed its CDN edge cache: median time-to-first-byte went from 0.42s to 2.39s. That was the bill for the crawler fix, it went in the report in bold, and the replacement caching layer became the next month's first ticket. Reports that only contain good news are not reports.
We retract our own findings when we are wrong
One audit reported a schema-to-visible-content mismatch. It was a brittle detection rule on our side. We re-verified all 116 schema questions across 16 pages, found every one had an exact visible counterpart, retracted the finding, and re-scored the affected categories in public.
The other side: an Indian coaching institute
From no blog, no schema and effectively no non-branded search presence, to page-one positions across its core cluster — including position 1.1 for "best colleges in hyderabad" and 1.9 for "top 10 junior colleges in hyderabad for mpc", with 136 non-branded page-one keywords, measured in Search Console over a 28-day window in April 2026.
The engine does not need you in the room.
A post every third day
Ten a month, each one written to a specific query from your calendar, in your site's design language, under your byline, with internal links, outbound citations and schema attached before it publishes.
A weekly health check
Schema still valid, llms.txt still served, robots rules intact, no accidental noindex, no dead internal links, security headers still set, publishing queue not stalled. Automated, logged, and alerted on failure.
A monthly re-audit and score delta
The full crawl again, scored on the same frozen rubric, published with the delta against both the previous month and the original baseline.
A monthly search performance scorecard
Live Search Console positions for your tracked keywords, what moved, what regressed, which new queries you started appearing for, and what the next month's calendar does about it.
Calendar re-planning
The calendar is not written once. Emerging queries you are already getting impressions for get promoted; posts that no longer earn their slot get cut.
Plugin maintenance
Schema kept current as your site changes, new page types added to the meta layer, and every fix from the gap register shipped as it clears.
You watch the whole thing from inside your own WordPress admin.
The Aglocom SEO Autopilot plugin is the visible half of the product. It applies the technical fixes, and it renders the dashboard: both scores against your frozen baseline, every category broken out, the open gap register, the publishing queue, live crawler-access status, and your Search Console trend since the day we started.
It also watches itself. If a Search Console grant gets revoked, a fix regresses, or the publishing queue stalls, the dashboard flags it rather than quietly reporting yesterday's number as if it were today's. A pipeline that has silently stopped is a failure, not a pass.
What we need from you, once.
Every grant goes to the dedicated Aglocom service account named in your kickoff email — never to an individual's personal account, so access survives staff changes on both sides. Read-only wherever read-only is enough.
Total time on your side: about twenty minutes on day zero, then roughly one hour a month to read the report and approve the next calendar.
Required
- Google Search Console — full user for our service account
- Google Analytics 4 — viewer access
- WordPress — an editor-or-above application password
- Ability to install one plugin
- The name and title of the person who signs off as author
Helpful, not blocking
- Google Ads read access, for real search volume in your market
- Firewall or CDN dashboard access, if a WAF sits in front of the site
- Your three main competitors, named
- Anything you sell that we must never claim, and anything you do not sell
₹20,000 a month. Month one is the proof.
No setup fee, no lock-in, no six-month minimum. Month one delivers the audit, the fixes, the plugin and the first posts. If the day-seven scorecard does not convince you, you stop, and you keep the plugin, the fixes and the content.
One site. Everything below, running continuously.
Add-ons, priced separately
- Google Business Profile management — for local "near me" demand, which content alone cannot capture
- Extra content volume — beyond ten posts a month
- Additional sites or subdomains — each one is its own baseline and calendar
- Paid media — if you want search and ads run as one funnel, that is our Admissions Growth System, not this
Not included — deliberately
- Google Business Profile management (add-on above)
- Paid advertising of any kind
- Landing page design or site rebuilds
- WhatsApp, email or CRM nurture
- Bought backlinks or link schemes — we do not touch them
We would rather lose the sale than have this argument in month three.
Who this works for.
A good fit
- WordPress sites with 20 or more pages and a real business behind them
- Companies whose buyers research before they buy — and increasingly research by asking an AI
- Teams with no in-house SEO, or one person carrying it alongside three other jobs
- Anyone who has paid for "SEO" and never received a number they could check
A bad fit
- Sites needing traffic this month — this compounds over quarters
- Businesses with no site, or one being rebuilt in the next 60 days
- Anyone who wants volume of posts as the deliverable rather than measured visibility
- Anyone expecting guaranteed positions — nobody can sell you those honestly
The things people actually ask.
Will I rank in seven days?
No, and you should distrust anyone who says otherwise. New pages typically take two to four weeks just to register in Search Console, and competitive positions move over months. Week one buys you a fixed foundation and a running engine, both of them measured. Ranking movement is a month two and three conversation, reported against the baseline we froze before touching anything.
Is the content AI-generated?
It is AI-drafted and human-governed. Every client gets a constitution file first: what you sell, what you do not sell, what may never be claimed, who the author is, and which numbers are allowed in writing with their source. Nothing publishes that contradicts it. We run that discipline on our own content too — after we published twelve posts containing a mis-framed metric, we built a claims gate and it has not happened since.
What happens to the plugin and the content if I stop?
You keep every published post and every fix already applied to your site — they are yours, on your domain. The plugin stops receiving updates, the dashboard stops refreshing, and publishing stops. Nothing is clawed back or deleted.
Why is this ₹20,000 when agencies quote much more?
Because the work is a system, not a headcount. The audit, the fixes, the writing, the publishing, the monitoring and the reporting all run as software with a human reviewing the output. You are paying for the system and the judgement, not for a team's timesheet.
Do you work outside education?
Yes. The system is vertical-agnostic — the same rubric and engine have been built and run for an Indian coaching institute and a US healthcare analytics company. The vertical only changes the constitution file and the keyword research. If you are a school or coaching institute wanting search and ads and nurture as one funnel, that is our Admissions Growth System instead.
What if my site is not WordPress?
The audit, scoring, research, content and reporting all work anywhere. The plugin does not — on other platforms the fixes are delivered as implementation tickets your developer applies, and the dashboard is delivered as a hosted report. Tell us your stack and we will be straight with you about which half you get.