Hyperlint Automation: Meta Description Fixes

[hyperlint-ai]

---

🪄 Experimental Hyperlint Feature - Read more 👇

This pull request is part of a series of Hyperlint automations to ease the burden of maintaining documentation.

We'll be introducing this automation, and others, over the coming months. These automations will always open pull requests(or issues) prior to making changes.

If this is not the change you want, please close this pull request.

⚠️ Important Note:
This feature may introduce erroneous changes (although we work really hard to make sure that doesn't happen). Please review the changes before merging.

❌ Limitations:
At this time, our bot can't respond to pull requests or issues.

📩 Need Help?
Please reach out to support with any requests, questions, or concerns.

[bllchmbrs]

@kodster28 @pedrosousa , meta descriptions! I believe this is the right format, let me know if not! Ignore the empty PR body, that will be fixed.

[cloudflare-workers-and-pages]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	f06f01d
Status:	✅  Deploy successful!
Preview URL:	https://da9ce7d3.cloudflare-docs-7ou.pages.dev
Branch Preview URL:	https://hyperlint-scan-meta-descript-ynxj.cloudflare-docs-7ou.pages.dev

View logs

[github-actions]

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/support/contacting-cloudflare-support/	https://hyperlint-scan-meta-descript-ynxj.cloudflare-docs-7ou.pages.dev/support/contacting-cloudflare-support/

[kodster28]

Howdy @bllchmbrs, lgtm.

Is there any way we could batch these to cover the whole of a folder at a time? So like one for all of /support, then /rules, then /dns etc.

If not, that's totally fine... just thinking that process-wise the meta description doesn't affect anything customer-facing + if it's adding something net new and less risky, so reviewing like 4000 PRs for all our pages might be a touch cumbersome.

There might be a similar thought / tradeoff / balance between these other types of things.... and it might vary for the type of ask / whether it's already a standard practice.

• Meta descriptions --> For us, not really used extensively, should prioritize for scale / adding a base level of them
• Alt text --> Generally there, might make sense to run over a folder to suggest improvements... or just gradually at one-off examples.
• Anchor links --> Generally there, gradually heal.

[holopin-bot]

Congratulations @Hyperlint-AI[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm69el9ll35750clcx8hoi8q0

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!