QueryRev Terms
Managed URL
A managed URL is QueryRev’s term for a page it looks after on a site you connected: the canonical version of the page, answering 200 with HTML, not a soft 404 and not excluded by you, that is indexable or has had search traffic in the last 90 days. Plans are measured in managed URLs.
- QueryRev’s own term
By QueryRev ResearchPublished Updated5 min read
Why it matters.
A site has far more URLs than pages. Redirects, parameter variants, error pages and files inflate any raw count, and a price based on URLs crawled would charge for noise. Counting only pages that can earn, or have earned, search traffic keeps the number close to what a team really works on, and makes it predictable.
Search engines draw a similar line. Google’s guide to crawl budget names duplicate content and soft 404 pages among the URLs that waste crawling[1], and a soft 404, a page that answers 200 while its content suggests an error, is flagged as a soft 404 error in Search Console[2].
One rule is deliberate: a page that had search traffic and then lost its indexing stays counted for 90 days. A noindex added by mistake to a page that earns money is exactly what should be flagged, not quietly dropped.
Status codes matter because they are the server’s own statement. In HTTP, 200 means the request succeeded[3]; a page that says “not found” with a 200 misleads every crawler. QueryRev’s study of AI crawler access applies the same rule to files: of the 6,294 sites whose robots.txt answer could be read, 5,637 had a file and 657 had none, and a web page served in place of the file was not counted as one[4].
A clear count also makes growth honest. When a site adds pages, the count rises with pages that can be found and read; when it adds filters or tracking parameters, it does not. A team can see which of the two happened without reading a crawl log.
How it is measured.
The count is taken once a day per site, from the latest crawl and the last 90 days of Search Console and analytics data. A workspace counts the sum of its sites. Not counted: redirects, pages canonicalised to another URL (see canonical URL), tracking-parameter variants, error pages and soft 404s, PDFs and other non-HTML files, and anything you exclude.
Each URL left out keeps its reason, so the difference between URLs found and URLs counted can be read line by line rather than taken on trust.
The count is a daily figure, so a change shows up the day it happens: a release that redirects a section lowers it, a new collection of indexable pages raises it, and a noindex added by mistake leaves it unchanged while the page is flagged.
Measured by
- Daily count per site
- Sum per workspace
A worked example.
Sample data: an invented site, to show the method.
A sample shop has 1,284 URLs. Of these, 246 are redirects, canonicalised copies, parameter variants, errors, files or excluded pages. The remaining 1,038 are its managed URLs.
The largest group left out is parameter variants from filtered navigation. When a new filter starts being crawled, the URLs found rise and the count does not, which is itself worth knowing.
What to do, step by step.
Start from the URLs a crawl finds, and from the URLs that Search Console and analytics show with traffic in the last 90 days.
Leave out redirects and URLs whose canonical points elsewhere: they stand for another page.
Leave out error pages, soft 404s and files that are not HTML, such as PDFs.
Leave out tracking and sorting variants that repeat a canonical page.
Keep the canonical HTML pages that are indexable, and those with search traffic in the last 90 days even if they lost their indexing.
Exclude by hand what you do not want looked after, and count again every day, so a change in the count is seen the day it happens.
Mistakes to avoid.
Counting URLs crawled. A raw crawl count includes every variant and error. It measures the crawler’s path, not the site.
Dropping a page the day it loses indexing. A page that earned traffic and was then set to noindex by mistake is the page to flag, not to forget.
Treating a soft 404 as a page. A not-found message served with the status 200 is an error page in disguise. Search engines leave it out, and so does the count.
Counting files as pages. PDFs, images and feeds can earn traffic, but they are not HTML pages a team edits, so they are not managed URLs.
How QueryRev treats it.
“Managed URL” is QueryRev’s own term, not an industry one. The inventory of managed pages gives every URL a state, and the daily count is shown in the product. Pricing is set by managed URLs, sites and client workspaces, never by tokens or AI credits.
Questions people ask.
Why are plans measured in managed URLs?
Because the count follows the pages a team really works on. A count of crawled URLs would charge for redirects and parameter noise, and a price in tokens or AI credits would change with how the product works rather than with the size of the site.
Is a managed URL the same as an indexed page?
No. An indexed page that later redirects stops counting, and a page that lost its indexing but had search traffic in the last 90 days still counts. The definition follows what deserves attention, not only what is indexed today.
What happens to the count when pages are removed?
A removed page that redirects or answers 404 stops counting from the next daily count. A page that only lost its indexing keeps counting for 90 days if it had search traffic, so the loss is flagged rather than hidden.
Sources and citation.
Primary sources only: the search engines, the AI vendors, standards bodies and QueryRev’s own research. Each is cited in the text by its number.
Optimize your crawl budgetGoogle Crawling Infrastructure ·
How HTTP status codes affect Google’s crawlersGoogle Crawling Infrastructure ·
RFC 9110: HTTP SemanticsIETF ·
State of AI crawler access, October 2026QueryRev Research ·
Cite this definition
A suggested citation. Its link goes to the definition, whose anchor does not change.
QueryRev Research. “Managed URL.” QueryRev AI glossary, 17 October 2026. https://queryrev.com/glossary/managed-url#definition
Related terms