Is Redirecting the Homepage to /general/index Bad Practice? First Clarify the Purpose and Approach

ProcrustesPR

Redirecting the homepage from the root URL to /general/index is not necessarily bad practice, and the destination path alone does not mean something is wrong with the website. The discussion offers differing views: some see this as an arrangement that accommodates a content management system (CMS), while others see it as a sign of poor CMS design. Start by asking why the redirect is needed. Then consider whether the public-facing homepage URL really needs to change, or whether the new homepage content could be served directly at the root URL. The responses also disagree on whether to use 301 or 302, so their recommendations should not be treated as general rules.

ProcrustesPRProcrustesPRShould You Use a Website Platform? Decide Based on Maintenance, Expansion, and Migration Needs

CMS limitations may explain the redirect without justifying the design

One response argues that redirecting to an internal path is not necessarily bad and offers two possible reasons: the CMS package needs to be installed in a subdirectory, or the system generates a custom homepage URL. That does not mean every website using the same path has the same requirements.

Another response explicitly presents a personal opinion: a CMS that requires the homepage to redirect to a subpath is poorly designed. The first response sees the arrangement as a possible consequence of system limitations; the second criticizes that very limitation. When encountering /general/index, it is worth checking:

  • Is this homepage location required by the CMS, or was it chosen for the website?
  • Does the redirect accommodate the installation location, or is the intention actually to move the homepage URL to that path?

The destination path alone cannot tell you whether to use 301 or 302

One response recommends using 301 when redirecting between domains with and without www, but 302 when redirecting from the root URL to /general/index. Another argues that the website described has made a definite decision to change how the URL is handled and should use 301, which indicates a permanent redirect. The two assessments differ.

These responses do not establish that homepage redirects to internal paths should always use 302—or always use 301. Even knowing that the destination is /general/index does not tell you whether the website intends to change its homepage location permanently. The discussion is a reminder to clarify the purpose before configuring a redirect, not a statement of current official guidance.

Using new homepage content may not require a new homepage URL

A third response accepts internal redirects but also suggests using .htaccess to serve the new homepage content in response to requests for the old homepage. The point is to consider which content to display separately from whether to redirect to another URL, rather than assuming both must change together.

However, that response provides no configuration example and does not say whether the website’s environment supports .htaccess, so this alternative still needs checking. For the website described, understanding the actual reason for the redirect before deciding whether to keep it is a better basis for judgment than the /general/index path alone.

ProcrustesPRProcrustesPRHow Do B2B Companies Use Blogs and Content Management Systems?

Redirecting the homepage to an internal path: perspectives from across the web

Will redirecting the homepage to an internal path affect search engine indexing?

This discussion alone cannot establish whether indexing will be affected in every case. One respondent argues that search engines can still index the website's pages and will replace the old homepage URL with /general/index. That is the respondent's assessment of the situation described, not an official guarantee from a search engine. The discussion provides no actual indexing results or conditions under which the claim applies, so it cannot establish that all websites would be unaffected.

ProcrustesPRHow Should a CMS Handle Images? From Upload Optimization to Descriptions and URL Management

References

  1. 302 Moved Temporarily or 301?webmasters.stackexchange.com — Source used in the article above.
  2. 302 Moved Temporarily or 301?webmasters.stackexchange.com — Source used in the article above.
  3. 302 Moved Temporarily or 301?webmasters.stackexchange.com — Discusses: Will redirecting the homepage to an internal path affect search engine indexing?

Related articles

Should You Use a Website Platform? Decide Based on Maintenance, Expansion, and Migration NeedsHow Do B2B Companies Use Blogs and Content Management Systems?How Should a CMS Handle Images? From Upload Optimization to Descriptions and URL ManagementWhat are the features, benefits, and limitations of a CMS?How does a headless CMS work, and what are its benefits and trade-offs?How to Choose Between Wix, WordPress.com, and WordPress.orgWhat types of WordPress are available, and what advantages does each offer for building a website?How can you build a responsive website without coding or Photoshop skills?
ProcrustesPR
ProcrustesPR