SEO family check failing: dev.yororis.com
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- devops
Research direction
Start by checking the SEO family check run linked in the issue, then compare the live app spec from doctl apps spec get <id> with .do/app.yaml. The check reports robots.txt and redirect headers missing noindex signals on the development host. Done when the development host disallows crawling and its robots.txt and redirect responses carry the required noindex signals, and the daily check passes.
Written by the indexing model from the issue text.
Description
The daily check of dev.yororis.com failed (https://github.com/krizaka/.github/actions/runs/39630607294).
If the log says noindex, Disallow: / or a missing sitemap, check APP_SEARCH_INDEXING in the live spec (doctl apps spec get <id>) and the repository's .do/app.yaml.
✗ dev host: robots.txt: a development host must Disallow: /
✗ dev host: robots.txt: no X-Robots-Tag noindex
✗ dev host: /: the redirect carries no X-Robots-Tag noindex
SEO family check: 3 problem(s) on 2 page(s) of https://dev.yororis.com
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 12m
- Merged PRs (30d)
- 144
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from krizaka/.github
-
paused
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
krizaka/.github#130 · 4 comments ·
Maintainers usually reply within 1 day
-
priority:P1 product:krizaka type:docs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
flannel-io/flannel#2608 ·
Maintainers usually reply within 2 days
-
Pin GitHub Actions to Ubuntu 26.04Possibly taken @krusty93 claimed this today. Openchore infra:workflow-automation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
diegosouzapw/OmniRoute#18387 ·
-
Enhancement: Test warm/fast reboot on supported Nexthop platformsPossibly taken @domingo-nexthop claimed this 119 days ago. OpenEnhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
sonic-net/sonic-mgmt#28842 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100