What we look for
The path of these addresses (the part after the domain) has the same part between slashes twice, such as /blog/blog/ or /shop/sale/shop/.
Why it matters
A repeat often comes from a link written without its leading slash, which stacks onto the current folder and can create endless new addresses for the same pages.
How to fix
Find where the link to each address comes from and correct it, usually by adding the leading slash so it starts from the site's root. Then send the repeated address to the right one with a 301 redirect (a permanent forwarding rule).
What it cannot know
Some repeats are deliberate, such as a date like /2024/05/05/. Raptor cannot tell those from mistakes.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: url.
repetitive_ path - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "url. repetitive_ path" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= url. repetitive_ path - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "url. repetitive_ path" }