I have disabled Pretty URLs for unruffled-sinoussi-fbd7d8.netlify.app (primary domain is tinyapps.org ), but .html-less continue to work and be indexed by search engines, causing duplicates to appear in search results, e.g., this Kagi Search returns two results for the same page, one with the .html e…

Thank you for your kind reply, hrishikesh . Is there not a way to prevent the pretty URLs from being generated? I’ve disabled the feature, and yet the links continue to exist. Or could a general 301 be set up in _redirects that adds an .html extension to any file without an extension?

You can use Edge Functions to handle this: [image] miles: Or could a general 301 be set up in _redirects that adds an .html extension to any file without an extension? but not with simple _redirects.

Thanks, @hrishikesh - I’ll look into those. Can you please tell me why there is even an option to enable or disable Pretty URLs (Site Configuration > Build & deploy > Post processing > Pretty URLs) when disabling them apparently does nothing?

I think you may be confused about what that option does. I think that turning it off does not prevent us from serving: https://site.com/file when you publish https://site.com/file.html leaving it off just does not redirect https://site.com/file.html to https://site.com/file So: turn it off, but…

Thanks for taking the time to reply here, @fool . Sadly, the previously-unknown-to-me Pretty URL feature must have been on for some time, as search engines have apparently indexed the .HTML-less links as well. It would be swell if those links did not exist at all (or at least could be redirected via …

To add to the offense, adding an explicit redirect to _redirects from /file to /file.html does not work, /file.html will still be served with HTTP 200 OK. I wonder if that is a bug or a feature. Does not seem to be documented anywhere.

Hi, @salomvary . How is something working exactly as designed and documented an “offense”? (I’m genuinely curious why you feel this way.) It is also not true that such redirects do not work. It definitely is possible to redirect from a URL ending in .html to one without it using redirect rules. Ple…

@luke The original “offense” was enabling the Pretty URLs feature for existing websites where it created potentially a large amount of duplicate content (from the SEO perspective), unless the website was already using canonical URLs. Opting everyone in to this feature was a heavy-handed move, and a …

Pretty URLs does not create any file. It is indeed a server-side rule.

Disabled Pretty URLS but .html-less links continue to work and be indexed by search engines

Support

hrishikesh September 23, 2023, 5:44pm 2

You can add a canonical tag: rel=canonical: the ultimate guide to canonical URLs • Yoast

Netlify Redirects Not Working for Forcing .html URLs

Topic		Replies	Views
Why does disabling Pretty URLs not disable Pretty URLs? Support building , deployment , redirects	10	1343	September 27, 2023
Netlify pretty urls won't strip .html extension Support building , deployment , redirects	10	7948	November 30, 2021
_redirects not working as expected Support redirects	2	112	July 21, 2025
When i visit my plain url of website its working but in end when i add .html its also working but making dublicate errors and affecting seo how to fix it Support redirects	1	45	May 20, 2025
Netlify Redirects Not Working for Forcing .html URLs Support building , deployment , netlify-newbie , redirects	3	150	May 12, 2025

Disabled Pretty URLS but .html-less links continue to work and be indexed by search engines

Related topics