Recognizes 1,500 crawlers, adds a watch list for your own bot and daily access alerts. Fixes two 1.0 issues: self-test requests counted as bot visits, and Settings switching the uninstall policy to delete.<\/p>","1.0.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.gif":{"filename":"icon-128x128.gif","revision":3730870,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.gif":{"filename":"icon-256x256.gif","revision":3730870,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3730870,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3730870,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3730870,"resolution":"1","location":"assets","locale":"","width":1440,"height":900},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3730870,"resolution":"2","location":"assets","locale":"","width":1440,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3730870,"resolution":"3","location":"assets","locale":"","width":1440,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3730870,"resolution":"4","location":"assets","locale":"","width":1440,"height":900},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3730870,"resolution":"5","location":"assets","locale":"","width":1440,"height":900},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3730870,"resolution":"6","location":"assets","locale":"","width":1440,"height":900},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3730870,"resolution":"7","location":"assets","locale":"","width":1440,"height":900}},"screenshots":{"1":"Dashboard: GEO score, AI access for ChatGPT, Claude, Perplexity and Google, the next fixes and 30 days of AI crawler visits.","2":"AI Visibility: access diagnosis, raw HTML coverage, crawl waste, time to first crawl.","3":"Crawlers: 1,500 known crawlers, your own watch list and an access test.","4":"Audit: category scores and findings, each with its reason and a concrete fix.","5":"AI access matrix, with every agent linked to its vendor's own documentation.","6":"llms.txt editor with self-grading and the honesty note.","7":"Setup: one check, then your results."}},"plugin_section":[],"plugin_tags":[264107,232780,247966,244604,12753],"plugin_category":[],"plugin_contributors":[277381],"plugin_business_model":[],"class_list":["post-357812","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-bots","plugin_tags-ai-crawler","plugin_tags-gptbot","plugin_tags-llms-txt","plugin_tags-robots-txt","plugin_contributors-tatilpanosu","plugin_committers-tatilpanosu"],"banners":{"banner":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/banner-772x250.png?rev=3730870","banner_2x":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/banner-1544x500.png?rev=3730870","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/icon-128x128.gif?rev=3730870","icon_2x":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/icon-256x256.gif?rev=3730870","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-1.png?rev=3730870","caption":"Dashboard: GEO score, AI access for ChatGPT, Claude, Perplexity and Google, the next fixes and 30 days of AI crawler visits."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-2.png?rev=3730870","caption":"AI Visibility: access diagnosis, raw HTML coverage, crawl waste, time to first crawl."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-3.png?rev=3730870","caption":"Crawlers: 1,500 known crawlers, your own watch list and an access test."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-4.png?rev=3730870","caption":"Audit: category scores and findings, each with its reason and a concrete fix."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-5.png?rev=3730870","caption":"AI access matrix, with every agent linked to its vendor's own documentation."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-6.png?rev=3730870","caption":"llms.txt editor with self-grading and the honesty note."},{"src":"https:\/\/ps.w.org\/turksem-geoseo\/assets\/screenshot-7.png?rev=3730870","caption":"Setup: one check, then your results."}],"raw_content":"\n
GEO SEO is an AI bot tracker and SEO audit plugin. It logs every visit from GPTBot, ClaudeBot, PerplexityBot, Googlebot and the rest of a 39-agent vendor-documented registry on your own server, and it recognizes 1,500 crawlers in total, from SEO tools to uptime monitors. It measures what each crawler could actually read, tells you when an AI crawler loses access, gives you allow and block controls, and shows whether your fixes changed anything. Honest by design.<\/p>\n\n
GEO SEO deals in evidence<\/strong>, not predictions or scores. Every number comes from your own server: what the crawler asked for, what your server actually returned, what it could actually read, and who actually arrived.<\/p>\n\n It closes the loop: measure<\/strong> how search and AI crawlers really use your site, audit<\/strong> your content and setup, fix<\/strong> what matters, and prove<\/strong> the effect with before\/after data.<\/p>\n\n GEO SEO makes no<\/strong> external requests by default. Three optional features talk to outside services, all off until you enable them:<\/p>\n\n The AI bot log and the audit run locally. The audit's checks for robots.txt, llms.txt, schema, crawler access and raw HTML visibility all use loopback requests to your own site only<\/strong>, sent from your own server.<\/p>\n\n One honest limit of that design, also stated in the plugin: whether that request passes through a CDN or firewall service in front of your site depends on how your domain resolves from your own server. When the answer comes back through a service it recognizes (Cloudflare, Sucuri, Imperva, Akamai, Fastly or Bunny CDN) and that service stops the test request, the plugin says so and does not count it as proof: those services recognize genuine crawlers by their network, and the test request comes from your server instead.<\/p>\n\n\n Turk SEM<\/a>, 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 full plugin page, including the bot identity note written for server administrators who find our user agent in their logs, is here<\/a>.<\/p><\/dd>\n 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. GEO SEO 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.<\/p><\/dd>\n No, and it does not try to. GEO SEO runs next to them: it reads their meta descriptions for its audit and disables its own schema output when they are active. Use GEO SEO for what they do not do: AI bot measurement, AI access control, and proof of change.<\/p><\/dd>\n 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 GEO SEO will not pretend otherwise.<\/p><\/dd>\n 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.<\/p><\/dd>\n Each front-end page view runs one early check on It is not. The AI bot log stores the bot name, page URL, timestamp, and a short one-way hash of the user agent string. For other crawlers, only the crawler's name, its category, the day and the visit counts are kept. IP addresses are never written to the database.<\/p><\/dd>\n Two lists. The first holds 39 AI agents, each documented by its own vendor and linked to that documentation: 37 crawlers plus the two permission tokens Google-Extended and Applebot-Extended, which never fetch anything. The second adds 1,463 crawlers from the open crawler-user-agents list (see Credits), covering SEO tools, search engines, monitors, feed readers and scripts. Entries that duplicate a documented AI agent are left out, so no visit is counted twice. Your own watch list comes on top.<\/p><\/dd>\n 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.<\/p><\/dd>\n If a physical 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.<\/p><\/dd>\nMeasure<\/h4>\n\n
\n
Audit<\/h4>\n\n
\n
Fix<\/h4>\n\n
\n
# BEGIN GEOSEO<\/code> block via the robots.txt filter. If a physical robots.txt file exists, GEO SEO 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.<\/li>\nContent Intelligence: your AI, your key<\/h4>\n\n
\n
Keep watching<\/h4>\n\n
\n
Prove<\/h4>\n\n
\n
Honest by design<\/h4>\n\n
\n
Credits<\/h4>\n\n
\n
External services<\/h3>\n\n
\n
api.indexnow.org<\/code> so participating search engines can fetch the change faster. No personal data is included. Service by Microsoft; see the IndexNow terms<\/a> and Microsoft privacy statement<\/a>.<\/li>\n\n
turksem-geoseo<\/code> inside \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Who makes GEO SEO?<\/h3><\/dt>\n
What is Generative Engine Optimization (GEO)?<\/h3><\/dt>\n
Does GEO SEO replace Yoast SEO or Rank Math?<\/h3><\/dt>\n
Can I block ChatGPT, Claude, or Perplexity from crawling my site?<\/h3><\/dt>\n
Does GEO SEO create an llms.txt file?<\/h3><\/dt>\n
Does it slow my site down?<\/h3><\/dt>\n
template_redirect<\/code>. For a regular visitor that is a single precompiled pattern match, measured at about 10 microseconds. A database write happens only when a known crawler matches: one row for an AI agent, one daily counter update for any other crawler. On very busy sites you can sample (log 1 in 5 or 1 in 10 requests). The audit runs in the admin, in batches.<\/p><\/dd>\nWhere is my visitors' personal data stored?<\/h3><\/dt>\n
Which crawlers does it recognize?<\/h3><\/dt>\n
What language is the interface in?<\/h3><\/dt>\n
My robots.txt or llms.txt did not change<\/h3><\/dt>\n
robots.txt<\/code> or llms.txt<\/code> file exists on your server, GEO SEO refuses to fight it and shows a warning instead. Delete or rename the physical file to let WordPress (and GEO SEO) serve it dynamically.<\/p><\/dd>\nSome bot visits seem to be missing<\/h3><\/dt>\n
How do I send feedback or report a problem?<\/h3><\/dt>\n