You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our cloud.gov URLs have been indexed by Google. They shouldn't be.
Seeing listings for non-official-looking URLs can lower confidence in us, our information
It dilutes our SEO—we're basically competing with ourselves with identical content
As those cloud.gov URLs change, those pages will 404
Possible solutions
Use Search Console to tell Google to remove those results and Webmaster Tools for Bing
Good: would be a fairly quick result
Drawbacks: This doesn't affect other search engines and I don't know how long the removal would stick—a month? a year?
Adjust robots.txt file based on hostname
Good: pretty quick, would work with every search engine
Drawbacks: Not every search engine honors the robots.txt file, but that's the case with all of these options. Could be complicated.
Change "noindex" meta tags based on host name
Good: Pretty solid solution
Drawbacks: I'm not sure how complicated it may be for Django, etc., to adjust page content based on current hostname when the environment is still 'prod'
Do a redirect from .cloud.gov/ to www.fec.gov/* if the agent is a search engine or social media
Good: Seems pretty solid, except…
Drawbacks: Not sure it's possible. We'd need to maintain the list of search engine (and social media) user agents.
Add canonical meta tags
Good: may be simple to implement, would address social media shares, too
Bad: ?
Considerations
Are there any files that we want to stay available or indexed at the cloud.gov url?
Do we need to update the og: and twitter: tags, too? I'm pretty sure they both honor the robots.txt file
After we've updated tags, I'd like to tell Google and Bing to re-crawl the site
Check our other cloud.gov domains to see where else we should apply this
How would each approach affect sharing content through social media? I wouldn't want to dump those clicks into a 404. This item feels like it could be a different ticket, like how to handle when people click a link to a cloud.gov page from a non-cloud.gov page? (I wouldn't want to send someone to www if they're intentionally working inside fec-*.cloud.gov
Screenshot
Completion criteria:
Old production routes, stage, and dev routes are now removed from search engines
The text was updated successfully, but these errors were encountered:
Summary
Our cloud.gov URLs have been indexed by Google. They shouldn't be.
Possible solutions
Considerations
Screenshot
Completion criteria:
The text was updated successfully, but these errors were encountered: