Search consoles tell you about classic web crawlers. Referral reports tell you who sent a click. Neither answers the quieter question teams now ask in Slack: which AI assistants fetched which pages this week, and how often? If you cannot see the fetch history, you are guessing which URLs matter to AI systems and which ones are invisible.
Rankify’s AI crawler log shows which assistants fetched which pages and how often, with day-by-day fetch history. It sits beside AI crawler control across 16 crawlers / 10 vendors. Free includes a 7-day log. Pro goes deeper, including verified identity on the control side. The log is separate from referral or arrival tracking. This post stays on the fetch and crawl log itself.
Rankify is the DaftPlug SEO and GEO plugin. This post is only about the AI crawler log (who fetched what, how often, day by day). Not IndexNow as a deep dive, not redirects, not schema graph, not title templates, not orphan pages, not FAQ blocks, not an llms.txt essay, not product schema, not local SEO. Those live elsewhere. For verifying crawler identity as part of the wider AI crawler control story, keep WordPress verified AI crawler identity nearby.
What Rankify actually ships here
Stay inside the real feature set:
- An AI crawler log that records which assistants fetched which pages and how often
- Day-by-day fetch history so you can see activity over time instead of a single opaque counter
- AI crawler control covering 16 crawlers / 10 vendors as the adjacent control surface (allow or manage crawlers; details of verification live in the related identity post)
- Free: 7-day log; Pro: deeper history, with verified identity available on the Pro control story
- Clear separation from referral / arrival tracking: this log is about fetches by AI crawlers, not about humans clicking through from a chat citation
This post does not invent undocumented export APIs Rankify does not publish here, per-URL AI ranking scores, or promises that every obscure bot on the internet appears in the 16 crawlers / 10 vendors set. The product promise is an AI crawler log with day-by-day history, free 7-day retention, Pro deeper history with verified identity in the wider control story, and separation from referral tracking. Stay there. IndexNow, redirects, schema graph, title templates, orphan pages, FAQ blocks, llms.txt essays, product schema, and local SEO are parallel tools, not this article’s job.
Why an AI crawler log matters on WordPress
You cannot improve what you never measure. Teams ship GEO experiments, update key pages, and still argue from anecdotes. A fetch log shows whether AI crawlers actually touched the URLs you care about.
Fetch is not the same as referral. A crawler can retrieve a page without sending a visitor afterward. Referral dashboards miss that. Rankify’s AI crawler log is intentionally separate from referral or arrival tracking so you do not confuse “was read by a bot” with “sent a click.”
Day-by-day history reveals streaks and silence. A spike after a launch, a quiet week after a robots change, or a single vendor that always hits the homepage first becomes visible when history is broken down by day.
Control without visibility is half a product. Rankify also offers AI crawler control across 16 crawlers / 10 vendors. The log tells you what happened. Control (and verified identity on Pro) helps you decide what should happen next. Read the related verified identity post when you are ready to harden who counts as a real vendor crawler.
Free versus Pro matches how serious the question is. A 7-day free log is enough to learn the habit. Deeper Pro history helps when you are comparing months, seasons, or long content programs.
WordPress sites are document-shaped. Posts, docs, and product pages are exactly the assets assistants retrieve. A WordPress-native log beats downloading raw server logs every Monday.
How to use the AI crawler log in wp-admin
Assume Rankify is installed and your site is publicly reachable. Give the log a few real days of traffic before you judge emptiness. Brand-new local sites will look quiet for honest reasons.
1. Open Rankify and find the AI crawler log
In wp-admin, open Rankify. Locate the AI crawler log surface. Confirm you are looking at fetch history for AI assistants, not a general hits counter and not a referral report. Mentally separate this view from classic search crawler reports you may keep elsewhere.
2. Learn the free 7-day window first
On free, expect 7 days of log history. Use that week to build a habit: which vendors appear, which URLs get fetched, whether product pages or blog posts dominate. If you need longer trends, Pro deeper history is the upgrade path. Do not invent retention numbers beyond free 7-day and Pro deeper history.
3. Read the log as “who fetched what, how often”
For each day you care about, note:
- Which assistants or vendor crawlers appear
- Which pages they fetched
- How often those fetches occurred
Look for concentration (one URL absorbing most fetches) and gaps (money pages with zero AI fetches while thin pages get hit). Gaps are not always bugs. They are signals for content, internal linking, or crawl control decisions.
4. Keep control and verification as a paired, separate pass
AI crawler control (16 crawlers / 10 vendors) and verified identity (Pro) sit next to the log. When you are ready to allow or restrict crawlers with stronger identity checks, follow the related verified identity post. This article’s job is reading the fetch log honestly before you twist control knobs blindly.
5. Smoke-test that the log is recording
- Confirm Rankify is active on the public site (not only on a hosts file staging alias nobody crawls).
- Wait for real AI crawler activity, or use whatever safe, allowed testing path you already trust. Do not attack third-party systems.
- Open the AI crawler log and confirm entries show assistant/vendor, page, and frequency context you can understand.
- Check day-by-day history across more than one day when traffic exists.
- On free, confirm you understand the 7-day window. On Pro, confirm deeper history is visible as expected.
- Open your referral or arrival reports separately and confirm you are not treating them as substitutes for the fetch log.
6. Document what you will review weekly
Write one line in your runbook: “Rankify AI crawler log reviewed on [cadence]. Free 7-day / Pro deeper history. Fetch log is not referral tracking. Control changes logged separately.” GEO work without a review cadence becomes folklore.
Who this is for
SEO and GEO leads who need evidence that AI crawlers touch priority URLs.
Content teams deciding which docs and posts deserve refresh investment.
WordPress site owners who hear “AI is reading us” and want receipts.
Agencies reporting to clients who ask about assistants and answer engines, not only classic blue links.
Anyone comparing free visibility now with Pro history later.
This is less urgent for private sites that block all AI crawlers and never intend to be retrieved. Even then, a short log window can confirm the block is working as you think.
What good looks like
- The AI crawler log shows which assistants fetched which pages and how often.
- Day-by-day history is readable for the retention window you have (7-day free, deeper on Pro).
- You can name at least one URL that gets frequent AI fetches and one important URL that does not.
- AI crawler control (16 crawlers / 10 vendors) remains available as an adjacent tool, with verified identity on the Pro story.
- Referral and arrival tracking stay conceptually separate from fetch history.
- IndexNow, redirects, schema graph, title templates, orphan pages, FAQ blocks, llms.txt essays, product schema, and local SEO deep dives were not required for this win.
- You did not invent universal bot coverage beyond the shipped crawler/vendor set, and you did not treat fetches as guaranteed citations or traffic.
If the log is empty for days on a busy public site, confirm Rankify is live on that hostname, confirm you are looking at the AI crawler log (not another report), and confirm you are not behind a setup that never receives those crawlers. Quiet can also be real. Do not fake data.
Pitfalls (the ones that bite)
Treating fetches like rankings. A fetch means retrieval happened. It does not mean you won a citation.
Reading referral reports instead of the crawl log. Different question, different tool. Rankify keeps them separate on purpose.
Panic-blocking every crawler after one noisy day. Read history first. Use control deliberately. Pair with verified identity when you need stronger assurance (related post).
Expecting infinite free history. Free is a 7-day log. Plan Pro if you need deeper history.
Judging a brand-new site after six hours. Give crawlers time. Compare week over week once the habit exists.
Ignoring money pages with zero fetches. The log’s silence is often the insight.
Bundling schema, redirects, and IndexNow into the same change window. You will not know what moved crawl interest. Read the log, change one GEO lever, read again.
Assuming every vendor bot is in scope. Rankify documents 16 crawlers / 10 vendors for control. Stay inside that product surface.
Practical checklist before you call it done
- Open Rankify’s AI crawler log on the production site.
- Confirm you understand free 7-day versus Pro deeper history.
- Note which assistants fetched which pages and how often for recent days.
- Separate that view from referral or arrival tracking.
- Flag one high-fetch URL and one important low-fetch URL for the content meeting.
- Review AI crawler control (16 crawlers / 10 vendors) only after you understand the log.
- When hardening identity, follow the verified identity related post (Pro).
- Set a weekly or biweekly log review cadence in the runbook.
- Leave IndexNow, redirects, schema graph, title templates, orphan pages, FAQ blocks, llms.txt essays, product schema, and local SEO for separate passes.
- Re-check after major robots, CDN, or firewall changes that might alter crawler access.
Takeaway
AI assistants retrieve WordPress pages whether or not your analytics celebrate it. Rankify’s AI crawler log shows which assistants fetched which pages and how often, with day-by-day history, a 7-day free window, deeper Pro history alongside verified identity in the wider control story, and a clean separation from referral tracking. Visibility first. Control second.
Rankify puts that fetch history in wp-admin so GEO conversations can use evidence. Open the log. Read a week. Decide which URLs deserve attention before you chase every new AI rumor.
One Pro membership unlocks Rankify plus Progressify, Lightify, Generatify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when you need deeper AI crawl history and verified crawler identity, not only a seven-day glimpse.
Open the AI crawler log. Name who fetched what yesterday. When that answer is boringly visible, your GEO practice finally has a memory.