Skip to content

Conversation

@thebiglabasky
Copy link
Contributor

Affected Components

  • Content & Marketing
  • Pricing
  • Test
  • Docs
  • Learn
  • Other

Notes for the Reviewer

  • Listed the page about subscribers which was missing. Added pricing caveats related to reaching limits for people to understand how that works.
  • Fixed some formatting (using where possible)
  • Adjusted some language for clarity
  • Added callouts for features requiring a paid plan

Copy link
Contributor

@MariadeAnton MariadeAnton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hope it helps @thebiglabasky, was as detailed as possible.

thebiglabasky and others added 2 commits December 1, 2025 16:11
Co-authored-by: María de Antón <[email protected]>
Co-authored-by: María de Antón <[email protected]>
@thebiglabasky
Copy link
Contributor Author

@MariadeAnton Changes are up!

Co-authored-by: María de Antón <[email protected]>
@thebiglabasky thebiglabasky removed the request for review from stefanjudis December 1, 2025 16:11
@thebiglabasky thebiglabasky merged commit f4c6197 into main Dec 1, 2025
3 checks passed
@thebiglabasky thebiglabasky deleted the sp-docs-improvements branch December 1, 2025 16:12
2. Create a CNAME record in your DNS that points to custom-domain.checkly-status-page.com
Any DNS provider will have the option to easily add CNAME records. For example on Cloudflare this looks as follows.
<Step title="Create a CNAME record that points to `custom-slug.checkly-status-page.com`">
Create a CNAME record with your DNS provider and point it to `custom-slug.checkly-status-page.com`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This has to be specifically custom-domain.checkly-status-page.com


3. Verify you are the owner of the domain by adding a `TXT` record to your DNS. The record can be copied from the status page configuration page after providing a custom domain and saving the page once.
<Step title="Verify domain ownership by adding a TXT record">
Copy the domain-verification TXT record from the Status Page configuration after you've added your custom domain and save the page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Copy the domain-verification TXT record from the Status Page configuration after you've added your custom domain and save the page.
Copy the domain-verification TXT record(s) from the Status Page configuration after you've added your custom domain and save the page.

4. Add validation `TXT` record(s). The record can be copied from the status page configuration page after providing a custom domain and saving the page once.
![Custom domain CNAME configuration](/images/docs/images/status-pages/status-pages-custom-domain-3.png)
<Note>
Search engines require this verification to index and list your Status Page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For search engine indexing, they'll need to verify ownership of their domain from the Google Console rather, the TXT for this is provided by Google during verification, not us. I'd say this step customers should be aware, but it would come after everything is set up already with the custom domain

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should update the accordingly then? Just trying to ensure we're not saying anything technically wrong for now

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I think we can either skip mentioning indexing at all, or mention it at the bottom after the custom domain setup details

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.

4 participants