Google Search Console ownership verification for App Platform domains

I have an App deployed and I have setup CNAME records for the “bare” and www domains ( and via Namecheap DNS. This works well after adding those domains to the app.

However, to verify ownership of the domain in the Google Search Console, I must add a TXT record on these same domains. This is not possible with an existing CNAME record.

I attempted to replace the CNAME record on the bare domain with both ALIAS and URL redirect records, however visiting the page returns a “404 Not Found” page with “Code: NoSuchWebsiteConfiguration”.

How are people setting up Google Search Console verification while also configuring CNAME DNS resolution for their Apps?

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

The 404 errors we’re indeed caused by DO issues with static sites and haven been fixed.

Using an ALIAS record for the bare domain does work correctly after this fix.

Kamal Nasser
DigitalOcean Employee
DigitalOcean Employee badge
April 7, 2021

Hi @arosiclair, the 404 Not Found error is unrelated, it was caused by an incident that has since been resolved: Intermittent 404 Errors with App Platform Static Sites.

The CNAME record that Google Search Console requires for ownership verification should not be identical to your actual site. But if that is not working, you can also use the HTML file or HTML tag methods.

Details on the different verification methods.

Site Moderator
Site Moderator badge
April 7, 2021

Hello, @arosiclair

If Namecheap DNS panel does not allow adding TXT records for domains that already have existing CNAME records you will need to find a workaround. I will recommend you to reach to their support team and ask if there is a solution.

An alternative is using our nameservers and control the DNS from your DigitalOcean account.

Hope that this helps! Regards, Alex

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel