You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Anchors are being stripped out (using sitemaps, linkExtractor and externalData) #1831
LINKS
Found 2 links matching your configuration
- https://example.com/page.html
- https://example.com/subpage.html
Expected behavior
Expected result:
LINKS
Found 3 links matching your configuration
- https://example.com/page.html
- https://example.com/subpage.html#/foo
- https://example.com/subpage.html#/bar
Note those are not section anchors. Those are actual pages, correctly parsed in URL Tester with the renderJavaScript: true option when passing the full URL with the anchor.
Thank you for a quick response!
Just for more clarity: we don't mind adding or implementing a custom linkExtractor or recordExtractor with custom set objectID. We just need those URLs to be accepted (crawling works as intended when manually running the crawl from the UI).
Somehow related, I tried to provide anchored URLs to the Crawler with externalData: ['myCSV], as described in your docs, and those URLs were again stripped down to one.
Single URL under Crawler admin > External Data: https://example.com/subpage.html
I would expect the same issue would appear with your API client (JS), but I've just successfully created 2 objects containing URLs with anchors in our demo app (free plan, app ID BZSKX72NEG). However, I was not able to create admin API key for our app (DOCSEARCH plan, app ID J1Y01X9HGM) because the "All API Keys" section/tab is missing. By using the Admin API key I received error 400 - Not enough rights to update an object near line:1.
So, technically, my wild guess would be your system supports anchored URLs, they are just not supported by the crawler?
changed the title [-]Anchors are being stripped out (using `sitemaps` and/or `linkExtractor`)[/-][+]Anchors are being stripped out (using `sitemaps`, `linkExtractor` and `externalData`)[/+]on Mar 30, 2023
Activity
shortcuts commentedon Mar 21, 2023
Hey, thanks for opening the issue. #1823 seems related.
I'll investigate if there's a way for us to differentiate hash routed pages from anchored sections
bojanrajh commentedon Mar 21, 2023
Thank you for a quick response!
Just for more clarity: we don't mind adding or implementing a custom
linkExtractororrecordExtractorwith custom setobjectID. We just need those URLs to be accepted (crawling works as intended when manually running the crawl from the UI).bojanrajh commentedon Mar 29, 2023
Hey @shortcuts, any news on this one?
Somehow related, I tried to provide anchored URLs to the Crawler with
externalData: ['myCSV],as described in your docs, and those URLs were again stripped down to one.Example CSV:
url;title;content "https://example.com/subpage.html#/foo";"Foo";"Foo content" "https://example.com/subpage.html#/bar";"Bar";"Bar content"Single URL under Crawler admin > External Data:
https://example.com/subpage.htmlI would expect the same issue would appear with your API client (JS), but I've just successfully created 2 objects containing URLs with anchors in our demo app (free plan, app ID
BZSKX72NEG). However, I was not able to create admin API key for our app (DOCSEARCH plan, app IDJ1Y01X9HGM) because the "All API Keys" section/tab is missing. By using the Admin API key I received error400 - Not enough rights to update an object near line:1.So, technically, my wild guess would be your system supports anchored URLs, they are just not supported by the crawler?
[-]Anchors are being stripped out (using `sitemaps` and/or `linkExtractor`)[/-][+]Anchors are being stripped out (using `sitemaps`, `linkExtractor` and `externalData`)[/+]bojanrajh commentedon Oct 16, 2023
Hey @shortcuts, and news about this one?