Someone asks ChatGPT a question. The answer cites your page. A few readers click through. In classic analytics, that visit often looks like direct traffic because the referrer was stripped. You cannot tell whether AI answers are sending people, which assistants matter, or which URLs win citations that convert into sessions. Rankify’s AI referral / answer-engine visit tracking attributes visits from ChatGPT, Perplexity, Claude, Gemini, and Copilot using tracking parameters assistants add, so you still count those sessions when the HTTP referrer is missing. That is different from logging which AI crawlers fetched pages.
Rankify is the DaftPlug SEO and GEO plugin. This post stays on AI visibility / referral tracking only. Not the AI crawler log (fetches), not crawler allow/block controls, not llms.txt, not IndexNow, not Local SEO, not redirects. Those are siblings on the same SEO/GEO list. A separate enablement may already cover fetch visibility (for example the AI crawler log for which pages were fetched). This article is referral-tracking-only.
What Rankify actually ships here
Stay inside the real feature set:
- AI referral / answer-engine visit tracking so you can see visits that arrived from AI answers
- Attribution for assistants such as ChatGPT, Perplexity, Claude, Gemini, and Copilot
- Tracking that uses parameters assistants add, so sessions can still count when the referrer is stripped
- A WordPress-native view of AI-driven visits that sits with Rankify’s broader visibility tools
- Clear separation from the AI crawler log (which records fetches), from crawler allow/block, from llms.txt, from IndexNow, from Local SEO, and from redirects
This post does not invent undocumented bid-management dashboards, guaranteed citation rank trackers, or promises that every assistant will always append parameters forever. The product promise is AI referral tracking for answer-engine visits, including when referrer is stripped, via the parameters assistants add. Stay there. Crawler log, crawler allow/block, llms.txt, IndexNow, Local SEO, and redirects are parallel tools, not this article’s job.
Why AI referral tracking matters on WordPress
Answer engines are a new discovery surface. People ask assistants instead of scrolling ten blue links. If your content is cited, some fraction of readers click. Without attribution, that fraction hides inside “direct.”
Referrer stripping is normal. Privacy rules, in-app browsers, and assistant UIs often omit or rewrite referrer. Classic “referring domain” reports undercount AI-driven sessions. Parameter-based tracking exists because referrer alone is no longer enough.
Fetches are not visits. An AI crawler retrieving a page for indexing or grounding is not the same event as a human clicking from an answer. Mixing those metrics leads to fake celebration (“we were crawled!”) or fake panic (“zero referral, so AI does not matter”). Rankify’s crawler log and referral tracking answer different questions on purpose.
Channel planning needs assistant-level signal. If Perplexity sends qualified trials and another assistant sends bounce-heavy curiosity clicks, your content and CTA strategy should differ. Tracking which assistant sent the visit is how that conversation becomes evidence.
Sibling GEO features solve different friction. Crawler allow/block and llms.txt shape what machines may read. IndexNow speeds discovery pings. Referral tracking measures human arrivals after an answer. Shipping all of them in one untested hour makes regression hunting painful. Enable referral tracking, verify attribution, then schedule crawler policy work on another day.
How to enable AI referral tracking in wp-admin
Assume Rankify is installed and you can compare analytics before/after on a staging or production site where you can generate a known test click (or wait for organic AI clicks). You will verify attribution in Rankify’s referral view, not only by staring at a third-party analytics “direct” bucket.
1. Separate the questions you want answered
Write two lines in the runbook before you touch settings:
- Crawler log question: which assistants or bots fetched which URLs?
- Referral tracking question: which answer engines sent human visits?
This post only answers the second. If someone on the team keeps asking about fetches, point them to the crawler log guide later. Do not enable every Rankify GEO toggle in the same hour.
2. Open Rankify and find AI referral / answer-engine visit tracking
In wp-admin, open Rankify. Locate AI referral tracking / answer-engine visit tracking among the SEO and GEO features Rankify exposes alongside the AI crawler log, crawler allow/block, llms.txt, IndexNow, Local SEO, and redirects. Turn referral tracking on for a first pass. Leave crawler log configuration, crawler allow/block, llms.txt, IndexNow, Local SEO, and redirects alone until referral attribution is verified.
3. Confirm how parameter-based attribution is meant to work
Read the in-product explanation Rankify provides for tracking parameters assistants add. The important product claim for this post is that visits can still count when referrer is stripped, because attribution is not solely dependent on HTTP referrer. Note that assistants and UIs evolve. Document what you verified on [date], not a forever guarantee that every client will always append the same parameters.
4. Smoke-test with a known AI-sourced click when you can
- From an assistant that supports outbound links with tracking parameters, open one of your URLs the way a reader would (or use a documented test path if Rankify exposes one).
- Land on the WordPress front end with cookies/analytics in a normal state.
- Confirm Rankify’s AI referral view records a visit attributed to the expected assistant family (ChatGPT, Perplexity, Claude, Gemini, Copilot, as applicable).
- Confirm a normal organic or typed visit does not get falsely labeled as an AI referral.
- If referrer is empty in your general analytics tool, confirm Rankify still attributed the AI visit via parameters.
If nothing appears, confirm referral tracking is enabled, confirm you actually arrived through an assistant link path that carries parameters, confirm caching layers are not stripping query strings you need for attribution, and re-test. Do not invent undocumented Rankify “force label all direct as ChatGPT” toggles that are not on the product page.
5. Keep the crawler log as a sibling, not a substitute
If the AI crawler log is already enabled, leave it as-is or schedule a separate review. Mentally label:
- AI referral tracking: human visits from answer engines
- AI crawler log: which pages assistants or crawlers fetched
- Crawler allow/block and llms.txt: policy for machine access
- IndexNow: ping-style discovery
- Local SEO and redirects: different SEO jobs entirely
Document all of that in the runbook so the next teammate does not disable referral tracking while debugging a robots rule.
6. Review the first meaningful window like an analyst
After enough traffic to matter (days or weeks depending on niche), review which assistants send visits and which URLs receive them. Compare to your top landing pages in classic search. Note pages that win AI visits but not Google clicks (or the reverse). That list becomes content and CTA homework, not a vanity screenshot.
7. Document the enablement for the next teammate
Write one line in your internal runbook: “Rankify AI referral tracking enabled on [date]. Verified assistants: [list]. Crawler log is separate. Re-test after major cache, CDN query-string, or analytics changes.” Referral tracking gets blamed when a CDN strips parameters and someone assumes AI traffic vanished.
Who this is for
Publishers and SaaS content teams investing in answer-engine visibility who need visit proof, not only crawl screenshots.
Ecommerce and product education sites that care whether AI answers send buyers or tire-kickers.
Agencies reporting GEO work to clients who ask “did ChatGPT send anyone?” with more rigor than a vibes-based direct-traffic glance.
SEO leads who already watch Search Console and need a parallel lens for assistant-driven sessions.
Privacy-conscious teams that know referrer is unreliable and want parameter-aware attribution inside WordPress.
This is less urgent for brand-new sites with almost no assistant citations yet, or for fully gated products with no public pages assistants can cite. Even then, enabling referral tracking early means you catch the first wave of AI visits instead of discovering them months later inside an unexplained direct spike.
What good looks like
- Rankify shows AI-attributed visits for assistants you care about (ChatGPT, Perplexity, Claude, Gemini, Copilot as they appear in your traffic).
- Sessions still attribute when classic analytics show a blank or direct referrer.
- Normal non-AI visits are not mislabeled as answer-engine traffic.
- You can name top URLs receiving AI visits without guessing from server logs alone.
- Referral tracking is enabled without requiring crawler allow/block, llms.txt, IndexNow, or Local SEO in the same change window.
- The team no longer confuses crawler fetches with human referral visits.
- You did not invent guaranteed citation rankings or claim every assistant will always send parameters.
If AI visits never appear despite known citations, confirm parameter preservation through cache/CDN, confirm the feature is on, and verify with a controlled assistant click path.
Pitfalls (the ones that bite)
Confusing referral tracking with the AI crawler log. Fetches are not visits. Debugging one while expecting the other wastes a quarter.
Enabling every Rankify GEO toggle with referral tracking. If referral tracking, crawler blocks, llms.txt, and IndexNow all land together, you cannot tell which change moved numbers. Enable referral tracking, verify, then add the next piece.
CDN or cache stripping query parameters. Parameter-based attribution dies when edge rules drop the query string. Whitelist what Rankify needs before declaring AI traffic “zero.”
Reading one day of data as strategy. AI visit volume can be spiky. Look at a window that matches your publish cadence.
Promising forever-perfect assistant coverage. Assistants change link formats. Document verified behavior; re-check after major UI shifts in those products.
Ignoring landing-page quality. Attribution without a usable page still bounces. Pair tracking with clear titles, scannable answers, and offers.
Forgetting to re-test after analytics or consent-banner changes. Tags and consent flows can alter what gets recorded. Behavior that worked last month can silently undercount.
Practical checklist before you call it done
- Confirm Rankify is installed and you can access the AI referral view.
- Write the “fetches vs visits” distinction in the runbook.
- In Rankify, enable AI referral / answer-engine visit tracking only for this pass.
- Leave AI crawler log deep configuration, crawler allow/block, llms.txt, IndexNow, Local SEO, and redirects alone if they are not already stable.
- Confirm cache/CDN rules preserve the query parameters attribution needs.
- Generate or wait for a known assistant click; confirm Rankify attributes the assistant family correctly.
- Confirm a normal direct or organic visit is not mislabeled as AI referral.
- Review top AI landing URLs after a meaningful traffic window.
- Treat crawler log as a sibling report, not a substitute metric.
- Re-test after CDN, cache, consent, or analytics changes.
- Write the enablement date and verified assistants in the team runbook.
- Only then consider enabling other Rankify GEO features that change crawler policy or discovery pings.
Takeaway
AI answers can send real readers while classic analytics call them direct. Rankify’s AI referral tracking attributes WordPress visits from ChatGPT, Perplexity, Claude, Gemini, and Copilot using parameters assistants add, so you still count sessions when referrer is stripped. It is not the crawler log, not llms.txt, and not IndexNow. It is the visit lens for answer-engine traffic.
Rankify handles AI referral tracking alongside the rest of the SEO and GEO stack, without asking you to guess from a blank referrer field. Enable it once. Verify with a real assistant click path and clean non-AI controls. Keep sibling GEO features as separate enablement work. For fetch visibility after referral tracking is stable, use the related AI crawler log for which pages were fetched guide when you are ready.
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 ChatGPT and other AI answers should show up as real visits in WordPress.
Turn referral tracking on. Click through from an assistant on purpose. When Rankify names the source and your generic analytics still says direct, you finally have the measurement layer answer engines actually require.