Should a WordPress blog on a new domain use a subdomain or a subdirectory?

For a portfolio website on a new domain with a WordPress blog sharing articles about the same area of expertise, a /blog/ subdirectory is the preferred starting point if the blog can be easily integrated into and maintained alongside the main site. This recommendation is based primarily on content relevance and ease of management, not on a claim that subdirectories necessarily rank higher. The supplied material contains clear disagreements about the SEO differences between the two structures. It does not justify claiming that subdomains will hurt rankings or that the two structures make no difference in every situation.

When articles and the portfolio cover the same subject, a subdirectory fits the content structure better

In a 2022 article, Semrush identifies content related to the main site as a suitable use case for subdirectories. If the content serves a distinctly different purpose or requires a particular CMS or design, a subdomain may be worth considering. This is a recommendation about site structure, not a statement of current search engine ranking rules.

In this scenario, the blog shares the very expertise showcased in the portfolio, so there is a reason to make it part of the main site. For example, using example.com/blog/ for articles about the design process alongside a design portfolio follows this approach of organizing content by relevance. However, this example is not evidence of ranking performance.

The argument about diluting existing authority does not directly apply to a new domain

Semrush material dated 2020 summarizes a traditional view held by some SEO practitioners: subdomains may not fully benefit from the backlinks accumulated by the main domain over many years. Rankings may therefore be weaker than with a subdirectory, particularly if no links are acquired separately for the subdomain.

This scenario, however, concerns a new domain with no existing content. The premise that years of accumulated links to the main site might not be shared cannot be applied directly, nor should the choice of structure for a new site be described as a loss caused by a site migration. This does not mean future linking arrangements are unimportant; rather, the material is insufficient to prove that choosing a subdomain puts a new site at an immediate disadvantage.

Meanwhile, several answers on Webmasters Stack Exchange argue that there is no significant SEO difference between the two structures, while another view is that subdomains dilute link value. These are participants’ claims, some of which relay other people’s opinions. The supplied excerpts are insufficient to establish how Google currently handles the two structures.

Check maintenance requirements before deciding whether to separate the blog

Specific reasons given in public discussions for preferring subdirectories include faster setup, easier maintenance, and generally fewer technical problems. Another answer notes that subdomains can point to different IP addresses, making it easier to manage large amounts of content separately. These reasons are context-dependent and should not be treated as universally applicable to every WordPress site.

• If the articles are closely related to the portfolio and maintaining them on the same site is convenient, evaluate /blog/ first.
• If the blog serves a distinctly different purpose or needs its own CMS, design, or management, a subdomain remains a reasonable option.
• If the sole expectation is that changing the URL structure will improve rankings, the available material cannot support that promise.