Skip to content

Remove Google Ads pages from the site#17978

Open
cnunciato wants to merge 1 commit intomasterfrom
cnunciato/remove-gads-pages
Open

Remove Google Ads pages from the site#17978
cnunciato wants to merge 1 commit intomasterfrom
cnunciato/remove-gads-pages

Conversation

@cnunciato
Copy link
Contributor

@cnunciato cnunciato commented Mar 14, 2026

These are no longer in use, so we can safely remove them.

Changes

  • Removed 31 gads landing pages under content/gads/
  • Removed 3 gads layout templates and 1 partial (gads-header.html)

These are no longer in use, so we don't need to keep them around anymore.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@claude
Copy link
Contributor

claude bot commented Mar 14, 2026

Docs Review

Scope: 31 gads content pages, 3 layout templates, and 1 partial removed (8,753 deletions, 0 additions).

Overall Assessment

Clean removal of unused Google Ads landing pages. No internal links reference any /gads/ paths, and all 31 deleted pages had block_external_search_index: true, so there's no SEO risk from removing them without redirects.

One item to verify

Non-gads aliases on the Azure page (content/gads/azure/index.md): This page defined aliases for /azure-resource-manager and /azure-infrastructure — root-level paths outside the /gads/ namespace. If any external campaigns, bookmarks, or paid ads still reference these URLs, they will now 404. Worth confirming these paths are no longer in use. If they need to be preserved, add S3 redirects (e.g., to /docs/clouds/aws/ or a relevant alternative page).

All other aliases were self-referential within /gads/ (mostly /gads/gads-template and /gads/neo), so they are fine to remove along with the content.

No other issues found

  • No internal links to /gads/ pages exist anywhere in the content, layouts, or config.
  • The layout files removed (gads/baseof.html, gads/gads-neo.html, gads/gads-template.html, partials/gads-header.html) are only used by the gads content type — no other pages reference them.
  • No existing S3 redirects reference gads paths.

Mention @claude for additional reviews or fixes.

@pulumi-bot
Copy link
Collaborator

@cnunciato cnunciato requested a review from alexleventer March 14, 2026 00:52
@cnunciato
Copy link
Contributor Author

cnunciato commented Mar 14, 2026

Claude confirms the potential issue called out in the review above:

No internal links point to /azure-resource-manager or /azure-infrastructure. The grep hits are just mentions of “Azure Resource Manager” and “Azure infrastructure” as text within blog posts and tutorials — not links to those paths. Safe to leave as-is.

@alexleventer
Copy link
Contributor

alexleventer commented Mar 14, 2026 via email

@cnunciato
Copy link
Contributor Author

Can we wait a couple days before making these changes?

Absolutely, no rush on this; they just keep coming up as we make changes to the website, so if they aren't in active use, it'd be good to clear 'em out. I checked a few weeks ago and it sounded like we were clear to do that, but that may have changed recently.

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

Successfully merging this pull request may close these issues.

3 participants