Submit Eciperay to Google Search Console (Stephen — account step)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 10/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- google-cloud, typescript
- Domain
- web-dev
Research direction
This issue requires Google Search Console access in Stephen’s Google account; no repository file or test is named. Read the SEO foundations issue and its sitemap follow-up to confirm when sitemap.xml is published, then verify www.eciperay.com and submit the sitemap. Done means ownership is verified, the sitemap is submitted, and the blocked and needs_human labels are removed.
Written by the indexing model from the issue text.
Description
For Stephen — account step (split from #304, 2026-11-03)
Stephen: when approving the #304 SSR plan you chose code changes only in #304, with this step raised separately for you.
What you need to do (in your own Google account):
- Verify www.eciperay.com in Google Search Console (add the property, complete ownership verification).
- Submit the site's
sitemap.xmlonce the SEO-foundations work publishes it (the sitemap artifact is tracked in its own follow-up issue, split from #304 at the same time as this one).
This is blocked on you because Search Console ownership lives in your Google account — there's no code-side substitute. Removing the blocked + needs_human labels (or saying so in chat) once submitted will close the loop.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 9h 12m
- Merged PRs (30d)
- 192
Getting set up
- Ships a 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 spudly/eciperay
-
bug priority-p1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
blocker bug in_progress priority-p1 qa
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
spudly/eciperay#425 · 4 comments ·
Maintainers usually reply within 1 day
-
blocked needs_human priority-p2
Difficulty 2/5 Half a day Newbie friendliness 68/100
spudly/eciperay#31 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 48/100
spudly/eciperay#419 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement in_progress priority-p2
Difficulty 4/5 3-5 days Newbie friendliness 55/100
spudly/eciperay#417 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Cleanup SetupPossibly taken @AlexanderKaran claimed this today. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
e18e/framework-tracker#769 ·
Maintainers usually reply within 1 day
-
bug v2
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/servers#5483 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
XiaomiMiMo/MiMo-Code#2783 ·
Maintainers usually reply within 1 day
-
area: web bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
kinqsradio/orbyn-engineering#227 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
joeldesante/TurfBuilder#258 ·
Maintainers usually reply within 1 day