Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move blogs to /blog #623

Open
danthelion opened this issue Jan 8, 2025 · 3 comments
Open

Move blogs to /blog #623

danthelion opened this issue Jan 8, 2025 · 3 comments

Comments

@danthelion
Copy link
Contributor

Moving to a /blog path can definitely have benefits, like improving URL structure and helping search engines and users better understand our content hierarchy. There might be some ranking or performance fluctuations but they’re typically short-lived if handled properly. I believe it’s worth doing for the long term...
Here’s what we need to keep in mind:

  1. Set up permanent (301) redirects carefully from the old URLs to the new /blog paths.
  2. Update all internal links to point directly to the /blog URLs in content, menus, and footers. (Can this be done in bulk?)
  3. Update XML sitemap with the new /blog URLs.
  4. Verify canonical tags on the new blog pages point to the correct /blog URLs.
  5. Verify that schema markups is still intact and reflects the new paths.
  6. Map old redirect URLs to their new /blog URLs to avoid redirect chains (e.g., A → B → C).
@danthelion
Copy link
Contributor Author

@travjenkins
Copy link
Member

I think we might want to wait for the Next JS migration to do this.

@Brenosalv
Copy link
Collaborator

Yes, with Gatsby we would need to use onPostBuild API on gatsby-node.js to fetch the slugs and add the redirects with them. In Next.js it will be different. So yeah, it might make sense to wait in case it's not so urgent.

@Brenosalv Brenosalv added this to the Migrate to next js milestone Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants