Use natural-language URLs, not IDs
Your page’s URL contains opaque IDs, hashes, or query strings instead of readable words. This is one of the few AI-visibility factors with hard numbers behind it: in Ahrefs’ study of 1.4 million ChatGPT prompts, search results with natural-language slugs were cited 89.8% of the time, versus 81.1% for opaque ones. Same content, different URL, measurably different citation rate.
Why does the URL text matter to AI?
Because the URL is judged before the page is opened. For each answer, ChatGPT retrieves dozens of candidate URLs and gathers only title, snippet, and URL - then cites about half of them.
There’s a gatekeeping layer before any page gets read, and the URL is one of the three signals doing the work at that gate. /blog/best-plumbers-austin/ tells the gatekeeper what the page is; /p?id=4823 tells it nothing.
What counts as a natural-language URL?
Lowercase words separated by hyphens, describing the page’s content:
- ✅
/services/emergency-plumbing/ - ✅
/learn/what-is-aio-in-seo/ - ❌
/index.php?page_id=4823 - ❌
/p/8f3a2c91d/ - ❌
/2026/07/18/8471/
How do you migrate without losing rankings?
Change the slug structure in your CMS (WordPress: Settings → Permalinks → “Post name”; most platforms have an equivalent), then 301-redirect every old URL to its new one - this transfers your existing search equity rather than abandoning it. Update internal links and your sitemap to the new URLs.
For a large site, migrate the pages that matter for AI answers first: services, products, and answer content.
New pages are free: just write the slug as words from day one. The URL is judged alongside your title tag at the same pre-click gate, so fix both together. Then rescan - this check is worth 5 points.
See where your site stands. The free scan takes about fifteen seconds and shows every fix.
Run a free AI visibility scan