Hey @webbrewjake we’ve had a look at this internally, and this subdomain atop our
netlify.com domain cannot be manually “Requested for Removal” within the tooling we have at our disposal.
This content/subdomain technically no longer lives on our .com domain, hence we’re unable to request removal from search engines of this non-existent property. In due time, googlebot (and other search engine crawlers) will continue to follow the 301 redirect to your subdomain atop our
netlify.app domain and then remove the .com subdomain reference altogether, on its own.
Worth a shot from your end:
- Signup for Google Search Console
- Add domain properties you’d like to manage
- Go through DNS TXT record or other verification
- Submit sitemaps and otherwise have control to manage your domains accordingly, going forward
I’m noticing some other, outdated .netlify.com references in-the-wild (https://www.facebook.com/hamiltonmassagecompany/posts/and-with-that-my-website-is-live-im-really-excited-to-have-this-up-and-running-o/479873989492107/), so it’d be worth your time to search around (
https://www.google.com/search?rlz=1C5CHFA_enUS875US875&ei=oLm1XqWiNdHT-wSzkYGoDw&q=Hamilton+Massage+Company+Sports+%22netlify.com%22&oq=Hamilton+Massage+Company+Sports+%22netlify.com%22&gs_lcp=CgZwc3ktYWIQAzoFCCEQqwJQmSVYuydgqSloAHAAeACAAU-IAd4CkgEBNZgBAKABAaoBB2d3cy13aXo&sclient=psy-ab&ved=0ahUKEwil8tu9hqXpAhXR6Z4KHbNIAPUQ4dUDCAw&uact=5) and update those, as well.
This Facebook example, in particular, and discrepancy in post content versus attached social card domains referenced is likely due to caching (use FB’s open graph debugger tool
to re-fetch open graph content) and/or combination of social meta tags (
<meta property="og:url" content="">
) needing optimized.
Obviously there’s a redirect chain from .com > .app > your custom domain, but it is resolving
correctly at your custom domain eventually. Understand the concerns here and hopefully this helps with some guidance and next steps you can take from your end. Best of luck!