Turksem GEOSEO – Generative Engine Optimization & SEO Audit
| 开发者 | tatilpanosu |
|---|---|
| 更新时间 | 2026年8月25日 21:09 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- AI bot activity log built on a registry of 39 agents, every one of them documented by its own vendor, with the source link shown next to each. We do not pad the list with user agents that do not exist, and the two permission tokens that never crawl (Google-Extended, Applebot-Extended) are labeled as exactly that.
- Access diagnosis: we fetch your own page as GPTBot, ClaudeBot, PerplexityBot and Googlebot and compare the answers. If a security plugin or a server rule quietly returns 403 or 429 to a crawler, your bot dashboard stays empty and nothing in robots.txt explains why. This test finds it.
- Raw HTML visibility: none of the major AI crawlers run JavaScript. We look for your posts' own sentences in the raw HTML and report what percentage survives, page by page.
- Crawl waste: how many of an agent's requests hit dead URLs. Measurements put AI crawlers around a third, against roughly a tenth for Googlebot.
- Time to first crawl after publishing, agents that used to visit and went quiet, and published pages no AI agent has ever fetched.
- Visitors arriving from AI services, caught both by referrer and by the address tag, because AI apps routinely strip the referrer.
- Privacy first: no IP addresses are ever stored. Only the agent name, category, page, HTTP status, and a one-way hash of the user agent.
- Site report card built from 90+ checks: titles, meta descriptions, duplicate H1s, missing image alt text, stale content, orphan pages, robots.txt hygiene, llms.txt quality, structured data inventory.
- Every finding comes with a plain-language "why it matters" and a concrete "how do I fix this", written for a site owner rather than a developer.
- Runs entirely from your WordPress database plus two loopback requests. No cloud crawler, no quota, no account.
- AI access matrix: allow or block each agent, written safely into a managed
# BEGIN GEOSEOblock via the robots.txt filter. If a physical robots.txt file exists, GEOSEO steps aside and tells you. The matrix also gets two widely misunderstood details right: Google-Extended and Applebot-Extended are permission tokens that never fetch anything and will never appear in your logs, and user-triggered fetchers such as ChatGPT-User and Perplexity-User state in their own vendor documentation that they may ignore robots.txt, so blocking them there may not stop them. - llms.txt generator with a built-in grader, and an honest note (see FAQ).
- IndexNow: ping search engines automatically when you publish or update content.
- Complementary schema: if no other SEO plugin outputs structured data, GEOSEO emits clean Organization, WebSite, and Article JSON-LD. If Yoast, Rank Math, AIOSEO, or SEOPress is active, GEOSEO's schema switches itself off: no duplicate markup, no meta box wars.
- Connect your own AI key (OpenAI, Anthropic, Google Gemini, or any OpenAI-compatible endpoint, including a local model) and have your posts reviewed through an E-E-A-T lens: signs of first-hand experience, depth of expertise, author identity, sourcing, freshness, answer clarity, originality, trust signals. Each finding comes with a concrete fix you can apply the same day.
- Why bring-your-own-key: with your own key this kind of review typically costs a few dollars a month, your content goes only to the provider you picked, and we are entirely out of the loop. There is no middleman account, no markup, and no subscription.
- Cost discipline built in: reviews run one post at a time on your click (never in bulk, never in the background), results are cached until the post changes, and a monthly cap that you control protects your bill.
- Honest framing, stated in the UI: these reviews are interpretation, not measurement. Two runs on the same post can differ. Our measured numbers stay on the evidence pages; the AI's judgment stays on this one.
- Change log: every fix you apply (robots rules, llms.txt publish, IndexNow on) is annotated with a timestamp.
- Audit history keeps your last 12 report cards, so you can see whether bot activity and scores moved after each change.
- We tell you what we cannot measure. Whether an AI names you in an answer, which questions people actually ask, how visible your competitors are: none of that is measurable from inside a WordPress install, and the same question returns different answers through the day. We will not invent a number for it.
- llms.txt does not move your score. You can publish one in a click, and the plugin tells you plainly that in a study of 137,000 domains, 97% of published files were never requested, that the biggest requester of those files is SEO audit tools rather than AI systems, and that Google states it does not use them.
- Structured data is offered as a correctness check, not an AI ranking lever. The best causal study on the question found no citation lift, and Google says no special markup is required.
- Content structure findings are labeled as what they are: observational evidence, not proven causation, and unhelpful for pages that already rank at the top.
- GEOSEO coexists with your current SEO plugin instead of demanding a migration.
安装:
- Upload the plugin ZIP via Plugins → Add New → Upload, or copy the
geoseofolder to/wp-content/plugins/. - Activate GEOSEO. The setup wizard opens automatically.
- Follow the four steps: first scan, turn on measuring, set up the fixes, prove and connect.
屏幕截图:
常见问题:
Who makes GEOSEO?
Turk SEM, an SEO agency that has been working on websites since 1999. We built this plugin for our own client work first, and every check in it started as a question we kept running into on real sites: why is the bot log empty, why does the crawler see a different page than the visitor, why did a fix change nothing. The plugin page, including the bot identity note written for server administrators who find our user agent in their logs, is at turksem.com/geoseo.
What is Generative Engine Optimization (GEO)?
Generative Engine Optimization is the work of getting your content read, understood, and used by AI systems such as ChatGPT, Claude, Perplexity, and Google's AI features. It has nothing to do with local or geographic SEO. GEOSEO covers the part of GEO you can measure from your own server: which AI crawlers come, what they can read, and what changed after each fix.
Does GEOSEO replace Yoast SEO or Rank Math?
No, and it does not try to. GEOSEO runs next to them: it reads their meta descriptions for its audit and disables its own schema output when they are active. Use GEOSEO for what they do not do: AI bot measurement, AI access control, and proof of change.
Can I block ChatGPT, Claude, or Perplexity from crawling my site?
Yes. The AI access matrix writes allow and block rules into a managed block of your robots.txt, one agent at a time. It also tells you when a block cannot work: user-triggered fetchers such as ChatGPT-User say in their own vendor documentation that they may ignore robots.txt, and GEOSEO will not pretend otherwise.
Does GEOSEO create an llms.txt file?
Yes, in one click, with a grader that scores the result. It also tells you plainly what llms.txt is unlikely to do for you today; the numbers are in the Honest by design section above.
Does it slow my site down?
The front-end hook is a single early-exit check on template_redirect with one database insert when a known bot matches. You can sample (log 1 in 5 or 1 in 10 requests) on very busy sites. The audit runs in the admin, in batches.
Where is my visitors' personal data stored?
It is not. The bot log stores the bot name, page URL, timestamp, and a short one-way hash of the user agent string. IP addresses are never written to the database.
What language is the interface in?
English, in this version. The admin copy ships from a reviewed, built-in table rather than translate.wordpress.org, because every audit sentence is written and checked alongside the check that produces it. More languages are planned; community translations may be adopted in a later version.
My robots.txt or llms.txt did not change
If a physical robots.txt or llms.txt file exists on your server, GEOSEO refuses to fight it and shows a warning instead. Delete or rename the physical file to let WordPress (and GEOSEO) serve it dynamically.
Some bot visits seem to be missing
If a full-page cache (a CDN or a caching plugin) serves the request, WordPress never runs and the visit cannot be logged. The dashboard states this openly. Counts are a reliable floor, not an exact total.
更新日志:
- First release: AI bot logging across a 39-agent vendor-documented registry, crawler access diagnosis, raw HTML visibility measurement, crawl waste, time to first crawl, silent-agent detection, AI referral tracking with address-tag fallback, site audit with 90+ checks, AI access matrix, llms.txt generator and grader, IndexNow, complementary schema, change annotations, audit history, setup wizard.