Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add an instruction to robots.txt to exclude docs search page #13652

Merged

Conversation

akbarkz
Copy link
Contributor

@akbarkz akbarkz commented Mar 7, 2024

Done

  • Added an instruction to robots.txt to exclude /server/docs/search* page since it's dynamic and doesn't need to be indexed by Google.

QA

  • Can be QA-ed after deployment by checking logs in Google Search Console. Currently there are a lot of 5xx and 403 errors coming from the page as Google is trying to index all the different search queries.

Help

QA steps - Commit guidelines

@webteam-app
Copy link

Demo starting at https://ubuntu-com-13652.demos.haus

Copy link

codecov bot commented Mar 7, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.43%. Comparing base (5868739) to head (9183a77).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #13652   +/-   ##
=======================================
  Coverage   74.43%   74.43%           
=======================================
  Files         107      107           
  Lines        2848     2848           
  Branches      948      948           
=======================================
  Hits         2120     2120           
  Misses        704      704           
  Partials       24       24           

@akbarkz akbarkz merged commit e423c3d into canonical:main Mar 7, 2024
15 checks passed
@carkod
Copy link
Contributor

carkod commented Mar 13, 2024

We may need to do this to every search endpoint if what was there Disallow: /search/* wasn't working. But I think we could use some kind of wildcard i.e. */docs/search/* (I made it up may need to be tested).

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