You are exploring AkOOre's demo website — read-only, nothing you change is saved.
URL structures — originaluniqueart.com — generated on Oct. 17, 2026, 1:31 a.m. by AkOOre
Overview · URL structures · originaluniqueart.com · 12 Oct 2026
600 of 620 URLs pass all four gates to the index.
Every URL of the sitemap and the homepage's links is grouped into 24 structures and put through four gates, in the order a crawler applies them. 20 URLs stop at a gate, in 7 structures. The indexability standing is 97%: 7 of 8 scored check points pass. Every count is a sample capped at a collection budget, never the site's page total.
What should I change first so that more of the site can be indexed?
Evidence
1recommendation(s), the worst first
0/1marked done by you. Marks stay until the next collection re-measures
the check, so a line you fixed shows struck through until the data agrees
with you.
2. Then improve (1)
Sitemap covers the site
(C. Coverage — what the collection found — this check scores 76/100)
What to do:
Add the missing URLs to the sitemap — every page worth indexing should be declared, not merely linked. If the missing ones are tracking variants or utility pages, exclude them from the site's navigation instead.
What we measured on your site:
480 of 633 unique URL(s) are declared in the sitemap; 167 homepage link(s) were merged in
Why it matters: The share of all collected URLs that the sitemap itself declares. URLs found only as homepage links live outside the sitemap — crawlers can still reach them, but the site is no longer telling its own story, and deeper pages with no links get missed entirely.
Why it comes here — robots.txt is read before anything is fetched, so a disallowed path is never downloaded and every later gate is unknowable for it.
What to do — A blocked URL can still appear in results as a bare address. To take these pages out of search, allow crawling and serve noindex instead; to make them rank, drop the Disallow line.
Why it comes here — We fetch one example URL per structure. A server error, a timeout and a user-agent block all count the same way here: no page, nothing to index.
What to do — Open the failing example URLs yourself. If they load in a browser but not for us, the server is filtering automated readers — that filter also catches the search engines.
Why it comes here — The meta robots tag and the X-Robots-Tag header, read together — search engines apply the most restrictive of the two, so one noindex anywhere closes the structure.
What to do — If these structures should rank, remove the noindex — the Indexability section says whether it comes from the meta tag or from the HTTP header.
Why it comes here — A page naming another URL as its canonical — or redirecting there — hands its ranking to that target and will not appear in results itself.
What to do — The right setup for tracking variants and duplicate listings, the wrong one for pages meant to rank. If a structure named here should rank on its own, fix its canonical tag or its redirect before anything else.
Where did the URL inventory come from, and how few shapes carry the site?
Terms used
URL structureSampleSitemap
Evidence · data collected 2026-10-12Good
76%declared in the sitemap
Scope of this audit
Every figure below the header is a statement about a sample. This is the sample: how big the site is estimated to be, how much of it AkOOre measured, and which of Google's own figures were available to check it against.
Estimated URLs on the site
646,345
estimate
extrapolated from the 100 of 16,033 sitemap files read (2,604 URLs listed in them)
URLs sampled
!
6 in depth · 3,669 stored
<0.01% of the estimate carry the full per-page audit (promoted pages); 0.6% are stored with the free light analysis
Sitemap URLs read
!
2,604 / 646,345
100 of 16,033 sitemap file(s) read by the page discovery pass
Templates sampled
!
4 / 24
URL structures with at least one promoted page, over the structures discovered; the 20 unsampled ones cover 591 collected URL(s), the largest being /en/art/*/, /en/articles/*/, /en/artists/groupby/*/, /en/art/groupby/*/, /en/art/list_category/*/
Languages sampled
!
1 / 32
languages the promoted pages are written in, over the languages the site declares (html lang and hreflang); not sampled: ar, bg, cs, da, de, el, es, et, fi, fr, hi, hr, hu, it, ja, ka, ko, lt, nl, no, pl, pt, ro, ru, sk, sl, sr, sv, tr, uk, zh
Google-indexed URLs
!
≥ 42 (0% of the estimate)
pages Google served at least once in the last 90 days — a floor of the index, since an indexed page nobody searched for is not counted Sitemaps in Search Console declare 972 URLs (Google no longer reports the indexed count per sitemap).
Googlebot log coverage
none
AkOOre reads no server logs, so crawl-frequency and crawl-budget statements in this report are inferred from sitemap dates, index status and robots rules, never measured
Page counts are estimates
AkOOre limits its own crawler, so what it stored is smaller than the site:
only 100 of the site's 16,033 sitemap files were read, so the URL total is extrapolated from those.
Weak
Read as a sample: the page-level findings come from the 6 promoted page(s), <0.01% of the site's estimated 646,345 URLs, spanning 4 of the 24 URL structures discovered. Promote a page of each unsampled structure (the pages list's Auto select does this first) to widen it.
Where these 633 URLs came from
480153
Declared in sitemap.xml —
480 URLs
(76%)Found only as a homepage link —
153 URLs
(24%)Named by both sources —
14, counted once
How few shapes carry the site
/en/art/*/30750%50% cum.
/en/articles/*/15124%74% cum.
/en/artists/groupby/*/254%78% cum.
/en/art/groupby/*/213%81% cum.
/en/art/list_category/*/173%84% cum.
the other 19 shapes9916%100% cum.
Sitemap.xml present and readable
Good100%
Whether the site publishes a sitemap.xml (or declares one in robots.txt) that actually lists pages. The sitemap is how a site TELLS crawlers what exists, instead of hoping they find every page by following links.
Found — the sitemap lists 480 URL(s) (reading capped at the collection budget)
Sitemap covers the site
Needs work76%
The share of all collected URLs that the sitemap itself declares. URLs found only as homepage links live outside the sitemap — crawlers can still reach them, but the site is no longer telling its own story, and deeper pages with no links get missed entirely.
Found — 480 of 633 unique URL(s) are declared in the sitemap; 167 homepage link(s) were merged in
How to fix:
Add the missing URLs to the sitemap — every page worth indexing should be declared, not merely linked. If the missing ones are tracking variants or utility pages, exclude them from the site's navigation instead.
URLs collected and grouped
Info
How many unique URLs the two sources yielded and how many structures they fold into. This is a SAMPLE, not the site's total page count — the sitemap read stops at a collection budget. A site of thousands of pages in a handful of structures is template-driven — each structure verdict below then speaks for many pages at once.
Found — 633 unique URL(s) sampled across 24 structure(s) — 480 from the sitemap, 167 homepage link(s); this is not the site's total URL count
Sitemaps read and site size estimate
Info
How many sitemap files the site publishes, how many AkOOre read, and how many page URLs they list. When a site has more sitemap files than the crawl budget reads, the total is extrapolated from the ones that were read — an estimate of the site's true size, not a page count.
Found — 16033 sitemap file(s) found, 100 read: 2604 URL(s) listed in the ones read — an estimated 646345 URL(s) across all sitemaps. 16 page(s) were loaded into this website's data (its limit is 5000)
Languages declared
Info
Which languages the site publishes in, read from the sample page of each retrieved structure: its html lang and the hreflang alternates it declares. A multilingual site has one version of every template per language, and each version can fail a gate on its own — the audit scope block says how many of them the promoted pages sample.
Found — 32 language(s) declared across the retrieved structures: ar, bg, cs, da, de, el, en, es, et, fi, fr, hi, hr, hu, it, ja, ka, ko, lt, nl, no, pl, pt, ro, ru, sk, sl, sr, sv, tr, uk, zh — 6 structure(s) declare hreflang alternates
The structures, in the order they matter
620 unique URLs
across 24
structures, biggest first — the same
weighting every percentage in this report uses.
The share of collected URLs whose structure robots.txt lets Googlebot fetch (judged on each structure's example path with the longest-match rule). A blocked URL is out before any other signal is read.
Found — 603 of 620 URL(s) allowed; blocked structures: /en/articles/show/*/, /core/complete-collection-index/, /en/accounts/profile/favorites/, /en/accounts/user_dashboard/
URLs answering with a real page
Good100%
Whether each allowed structure's example URL served an actual page to our retriever. A structure that errors or walls out automated readers is invisible to crawlers no matter what its instructions say.
Found — 1 structure(s) did not answer: /cdn-cgi/l/email-protection/
The share of retrieved URLs whose pages do NOT say noindex — in the meta robots tag or the X-Robots-Tag header; search engines apply the most restrictive of the two. A noindexed structure is a whole slice of the site excluded by its own instruction.
Found — 1 structure(s) noindexed: /en/*/list/
URLs whose links are followed
Good100%
The share of retrieved URLs without a nofollow instruction. Page-wide nofollow cuts the site's internal linking: crawlers stop passing through those pages to find the rest.
Found — no page-wide nofollow found
URLs that are their own canonical
Good100%
The share of retrieved URLs that are their own canonical — they neither declare another URL as the official version nor redirect to one. A structure canonicalized elsewhere hands its ranking to the target and will not appear in results itself.
Found — 1 structure(s) point elsewhere: /
Signals coherent
Good100%
Whether robots.txt, the meta robots tag, the X-Robots-Tag header and the canonical tell one story per structure. Contradictions resolve silently (the most restrictive signal wins), which is exactly how a page ends up unindexed without anyone having decided it.
Found — 2 structure(s) with contradictions or warnings: /, /en/*/list/ — the findings card below spells each one out
Contradictions & comments
/en/articles/show/*/
14 URLs decided by this
— 2% of the collected sample
Blocked by robots.txt. Blocked pages can still appear in results as bare URLs; if they must disappear entirely, allow crawling and serve noindex instead — and if they should rank, remove the robots.txt rule.
/
1 URL decided by this
— 0% of the collected sample
These pages declare another URL as their canonical (or redirect to one), so this structure itself will not rank — search engines index the canonical target instead. If these pages should rank on their own, make them self-canonical.
/cdn-cgi/l/email-protection/
1 URL decided by this
— 0% of the collected sample
The example URL did not answer our retriever — a structure that does not serve pages cannot be indexed. Check whether the server errors or blocks automated readers.
/core/complete-collection-index/
1 URL decided by this
— 0% of the collected sample
Blocked by robots.txt. Blocked pages can still appear in results as bare URLs; if they must disappear entirely, allow crawling and serve noindex instead — and if they should rank, remove the robots.txt rule.
/en/*/list/
1 URL decided by this
— 0% of the collected sample
Crawlable but noindexed: crawlers spend budget on these pages without ever indexing them. Fine if deliberate — if these pages should rank, remove the noindex.
/en/accounts/profile/favorites/
1 URL decided by this
— 0% of the collected sample
Blocked by robots.txt. Blocked pages can still appear in results as bare URLs; if they must disappear entirely, allow crawling and serve noindex instead — and if they should rank, remove the robots.txt rule.
/en/accounts/user_dashboard/
1 URL decided by this
— 0% of the collected sample
Blocked by robots.txt. Blocked pages can still appear in results as bare URLs; if they must disappear entirely, allow crawling and serve noindex instead — and if they should rank, remove the robots.txt rule.
What do the words the gates, the log and the ledger use mean?
The shape
URL structure
A path shape shared by many URLs: /en/art/*/ with a count
of 339 means 339 collected URLs differ only in the segment written
*. Template-driven sites fold thousands of pages into a
handful of shapes, so one verdict describes a whole slice of the site.
Each shape is judged through one randomly chosen example URL.
The inventory
Sample, not inventory
The URL list is a sample: everything the
sitemap.xml declares (nested indexes followed, reading capped
at a collection budget) plus every internal link on the homepage, merged
and deduplicated. A site larger than that budget will always show fewer
URLs here than it has, and no figure on this page should be read as its
page count.
Why gates
Why an order, not seven columns
The checks are not independent. robots.txt is read before anything is
fetched; a page never fetched has no meta robots tag; a page nobody may
index has no canonical worth arguing about. The order makes the empty
squares honest — they mean the question was never reachable, not that the
shape passed — and it says where to start, because a fix at gate 1 can
change every verdict behind it.
Gate 1
robots.txt
Whether your robots.txt lets Googlebot
fetch the shape's example path, by the longest-match rule real crawlers
apply. Blocked means the pages are never downloaded — and a
blocked URL can still appear in results as a bare address. To take pages
out of search, allow crawling and serve noindex instead.
Gate 2
Retrieval
Whether the example URL served a real page to our retriever. A server
error, a timeout and a bot wall all count the same: no page. If a URL
loads in your browser but fails here, the server is filtering automated
readers — and search engine crawlers are automated readers.
Gate 3
Meta robots and X-Robots-Tag
The same two directives (noindex, nofollow)
in two places: a tag in the HTML, and a header on the HTTP response —
a third place indexing is decided, invisible in the page source. We read
the header with one HEAD request per retrieved sample. Most servers send
none, which is the index, follow default and shows as
nothing sent. When the two disagree, the most restrictive
wins.
Gate 4
Canonical
A page can declare, with <link rel="canonical">,
which URL is the official version of its content — and search engines
index that one. Itself means the example URL declares itself, or
declares nothing at all (the default), and does not redirect.
Points elsewhere means the shape hands its ranking to another
URL: right for tracking variants and duplicates, wrong for pages meant to
rank.
The standing
Weighted by URL count
The report's question is "what share of the site's URLs is indexable",
not "what share of the table's rows". A blocked shape of 50 URLs matters
fifty times more than a blocked one-off path — so every percentage here,
the ladder included, counts URLs.
The limits
One example per shape
Exact where a template gives every page the same rules, approximate
where a shape mixes them: a robots.txt blocking only part of
/en/orders/… can flip that shape's verdict between runs
depending on which example was drawn. When a verdict surprises you, open
the example URL and a few of its siblings before changing anything.
What does the ladder mean for this site, and what should change first?
Findings · 2026-10-12
What is indexable today
Currently, 600 URLs (97% of everything collected) are fully indexable and can pass through every technical gate to appear in search results. The most significant reduction in your crawlable footprint occurs at the robots.txt gate, where 17 URLs are stopped from being processed. The surviving indexable content is largely comprised of structures like /en/art/*/, which accounts for 307 of the 620 total URLs collected. It is also worth noting that while a sitemap is present, it only declares 480 of 633 unique URLs, meaning many indexable pages are not listed in the sitemap.
What is costing you
/en/articles/show/*: 14 URLs are currently blocked by robots.txt, preventing them from being indexed.
/cdn-cgi/l/email-protection/: 1 URL failed to answer the retriever, resulting in a failed retrieval.
/: 1 URL has a foreign canonical, which prevents this specific structure from ranking.
/en/*/list/: 1 URL is restricted by a meta noindex, meaning crawlers spend budget on it without indexing it.
/core/complete-collection-index/: 1 URL is currently blocked by robots.txt, preventing its discovery.
What is a choice, not a bug
Several exclusions in the URL structure appear to be deliberate administrative choices rather than technical errors. The blocks on utility and private paths, specifically /en/accounts/user_dashboard/, /en/accounts/profile/favorites/, and /core/complete-collection-index/, serve to protect user data or manage site utility. These restrictions are consistent with a policy of excluding non-public or low-value paths from search engine visibility.
AkBot will be asked
AkOOre isn't open yet
AkOOre opens on November 1, 2026. Check back then to create your account.
AkOOre assistantAI · answers in a few seconds
Hi! I can tell you what AkOOre does for your website and how to get started. What would you like to know?