Is there a way to prevent long style URLs from being scanned?
Yes, we're using URI Management, the short URL style for now(productcode.html). Just got a report of errors for scanned pages that didn't load correctly, as in no Style sheets. The errors were responsive violations such as Objects too close, etc. I'm also not sure how they were scanned even though I'm not sure they weren't accidentally submitted in a sitemap file. These pages don't need to be fixed to solve the issue. I think they need to be prevented from being scanned. The URLs turned out to be a Merchant long URL and generated internally, such as when loading up an UpSale or Gift Cert page. Or, it's an old URL because it has a session_ID and session_IDs are no longer used in the URLs. I never knew why the previous agency used them.
Is there some robot.txt command? Or if need be, an htaccess instruction?
Scott
Yes, we're using URI Management, the short URL style for now(productcode.html). Just got a report of errors for scanned pages that didn't load correctly, as in no Style sheets. The errors were responsive violations such as Objects too close, etc. I'm also not sure how they were scanned even though I'm not sure they weren't accidentally submitted in a sitemap file. These pages don't need to be fixed to solve the issue. I think they need to be prevented from being scanned. The URLs turned out to be a Merchant long URL and generated internally, such as when loading up an UpSale or Gift Cert page. Or, it's an old URL because it has a session_ID and session_IDs are no longer used in the URLs. I never knew why the previous agency used them.
Is there some robot.txt command? Or if need be, an htaccess instruction?
Scott
Comment