Whether you change example.com/about.php to example.com/about or replace .shtml with .php, the key point is that the URL has changed, and the old URL must redirect to the corresponding new page. The public discussions cited here recommend 301 permanent redirects so users can still find the content through old links and bookmarks, and search engines know where the page has moved. These discussions do not, however, establish that rankings will stay the same or that removing extensions alone improves SEO.
An extension’s effect on rankings is separate from the risks of changing a URL
When a live URL changes, links stored by search engines and external websites do not automatically update. If the old URL no longer serves content and has no redirect, search results or bookmarks may lead users to a broken page. This is the issue to prioritize during migration.
As for whether .html or .php affects rankings, these discussions offer no consistent, evidence-based conclusion. One respondent argues that even if extensions are indexed, their impact is minimal. Another speculates that retaining extensions helps identify document types, while a reply points out that document types have long been independent of URL extensions. Neither “keeping .html offers a ranking advantage” nor “removing .php improves rankings” should therefore be treated as an established rule.
Map old URLs to new ones before setting up 301 redirects
For a change from /about.php to /about, the specific recommendation in the discussions is to redirect the old path to the new one using a 301. Making the new URL accessible is not enough; users following the old URL must also reach the corresponding content.
- Removing only the extension: /about.php maps to /about, and the old URL should redirect to the new location of the same content.
- Changing the extension: /file.shtml maps to /file.php. The old URL still needs a redirect; simply publishing the new page is not enough.
- Changing the filename or path as well: Do not assume that removing the extension will lead to the new page. First confirm the new location for each old URL.
The cited discussions provide .htaccess and RewriteRule examples, but not every website can use them as written. For a rewrite from Web Forms to MVC 3, the discussions support redirecting old URLs to new ones with 301 redirects, but do not provide complete configuration instructions for that deployment environment.
Keeping URLs consistent over time is a better-supported reason to remove extensions
Some respondents argue that URLs should not be tied to the technology used to generate pages. For example, a site using PHP today should not have to change its public URLs again if it switches to another technology later. Reasons to remove extensions can include easier maintenance, consistent URLs, and a lower risk of broken links when technology changes—not a promise of improved rankings.
When explaining the issue to a manager, discuss “whether to keep .html” separately from “how to keep old links working.” Large websites that do not use .html are design examples, not proof of a ranking effect. The community discussions cited here support the recommendation to handle old URLs during migration, but they are not a current official guarantee from search engines.
Changing URL extensions and SEO: perspectives from across the web
If about.php changes to about, will all its accumulated SEO value disappear?
Not necessarily, but rankings are not guaranteed to stay the same either. The public discussions recommend redirecting the old URL to the corresponding new page with a 301. One respondent believes search engines will transfer the value of old links to the new URL, with a small loss in the process. That is a community opinion, not enough to establish whether any loss would occur today or how large it would be, or to guarantee actual rankings.
When rewriting a Web Forms site in MVC 3, will removing .html and setting up 301 redirects ensure that SEO is unaffected?
No. The public discussions suggest that changing URLs on a live website may affect search performance. They recommend 301 redirects from old URLs to the corresponding new pages so search engines and users do not encounter broken pages. These discussions provide neither complete configuration instructions for the MVC 3 deployment environment nor migration results, so they cannot establish that rankings will stay the same.
Is there conclusive evidence about rankings to present to a manager when discussing whether to keep .html?
The discussions cited here do not provide sufficient empirical evidence to establish a ranking effect. One respondent believes extensions are indexed but have a minimal impact on rankings. Another speculates that retaining extensions may help search engines identify document types, while a reply points out that document types have long been independent of URL extensions. Large websites that do not use .html can serve as design examples, but their choice does not prove that omitting the extension affects rankings.
References
- Will changing SHTML files to PHP change effect how search engines index my site?webmasters.stackexchange.com — Source used in the article above.
- SEO .html, .php or nothingwebmasters.stackexchange.com — Discusses: Is there conclusive evidence about rankings to present to a manager when discussing whether to keep .html?
- SEO - Changing file extensionwebmasters.stackexchange.com — Source used in the article above.
- SEO .html, .php or nothingwebmasters.stackexchange.com — Source used in the article above.
- .html extension or no for SEO purposeswebmasters.stackexchange.com — Discusses: Is there conclusive evidence about rankings to present to a manager when discussing whether to keep .html?
- .html extension or no for SEO purposeswebmasters.stackexchange.com — Discusses: Is there conclusive evidence about rankings to present to a manager when discussing whether to keep .html?
- Is SEO effected when URL changes from .php to not including .phpwebmasters.stackexchange.com — Discusses: If about.php changes to about, will all its accumulated SEO value disappear?
- .html extension or no for SEO purposeswebmasters.stackexchange.com — Discusses: Is there conclusive evidence about rankings to present to a manager when discussing whether to keep .html?
- SEO - Changing file extensionwebmasters.stackexchange.com — Discusses: When rewriting a Web Forms site in MVC 3, will removing .html and setting up 301 redirects ensure that SEO is unaffected?
- SEO - Changing file extensionwebmasters.stackexchange.com — Discusses: If about.php changes to about, will all its accumulated SEO value disappear?; When rewriting a Web Forms site in MVC 3, will removing .html and setting up 301 redirects ensure that SEO is unaffected?




