The decision that matters
Use a main-site path when the blog shares the brand, audience and publishing workflow of the marketing site. This can simplify navigation, templates and internal linking. A subdomain may suit a genuinely separate application or team with different operational requirements. Neither URL pattern removes the need for useful content, crawlable links and consistent canonical URLs. Do not publish duplicate copies without a deliberate canonical or redirect strategy.
A practical scenario
For a studio whose articles explain its services, a path such as /blogs keeps the journal close to service pages and project references. Each article can link naturally to relevant expertise. If an older blog subdomain exists, map its existing article URLs to the new equivalents rather than redirecting every page indiscriminately to the homepage.
Before you ship
- Choose one canonical location for each article.
- Include articles in the site’s navigation and sitemap.
- Plan redirects for existing URLs before moving content.
A useful next step
Document the publishing location and URL convention before writing the first batch. Keep slugs stable and descriptive. Evaluate the decision by how well people and crawlers can discover the content, not by an unsupported claim that one structure always ranks higher.
Primary reference & further reading
This guide combines general engineering recommendations with an illustrative scenario. Provider behavior can change; check current documentation before applying it. Read our editorial approach.