[FEATURE]: SEO & SEM optimization sitemap, robots.txt, per-article metadata, and structured data
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- next.js, typescript
Research direction
Start by reading app/a/[slug]/page.tsx, app/layout.tsx, and the articles-index.json data source, then review the existing static-export setup. Implement the sitemap, robots rules, per-article metadata, structured data, verification tag, and manifest described in the issue, splitting the work if needed. Done means the listed routes and page metadata exist and the supplied Rich Results, Search Console, and PageSpeed tools can validate the result.
Written by the indexing model from the issue text.
Description
Feature and its Use Cases
Since Stable Viewpoints is a blogging platform, SEO is pretty much the lifeline for organic traffic. Right now the site is missing some fundamental pieces that prevent search engines from properly indexing and ranking the articles.
I checked the live site and found these gaps:
- No
sitemap.xml:viewpoints.stability.nexus/sitemap.xmlreturns 404. Google literally can't discover our articles. - No
robots.txt:viewpoints.stability.nexus/robots.txtalso 404. No crawl instructions for any bot. - Every article shows the same title and description in search results : The
<title>tag on all article pages just says "Stable Viewpoints" instead of the actual article title. Same issue with meta descriptions. This is becauseapp/a/[slug]/page.tsxdoesn't export agenerateMetadatafunction. - Canonical URLs on all articles point to the homepage (
/) : This makes Google think every article is a duplicate of the homepage. Huge ranking penalty. - No JSON-LD structured data : No
BlogPostingorWebSiteschema, so we'll never get rich results (article cards, breadcrumbs, etc.) in search. - No Google Search Console verification : We can't even monitor how Google sees the site.
What needs to be done
- Add
app/sitemap.ts: Generate sitemap fromarticles-index.jsonwith all article URLs, dates, and priorities - Add
app/robots.ts: Allow all crawlers, link to sitemap - Add
generateMetadata()toapp/a/[slug]/page.tsx: Per-article title, description, OG tags, Twitter cards, and canonical URL - Add JSON-LD structured data :
WebSite+Organizationon homepage,BlogPostingschema on each article page - Add Google Search Console verification tag in
app/layout.tsx - Add
public/manifest.jsonand link it in layout
How users (and the project) benefit
- Articles actually show up in Google search with proper titles and descriptions
- Each article gets its own rich preview when shared on Twitter/LinkedIn/Discord
- GSC gives us data on impressions, clicks, and indexing issues
- Sitemap lets Google discover new articles automatically after deploy
I'd suggest splitting this into 2-3 PRs by priority. happy to pick some of these up.
Additional Context
I used my own portfolio https://atharvanaik.me as a reference : it's built with the same stack (Next.js 15, App Router, static export) and has all of these implemented. Here are the specific files for reference:
- sitemap.ts : dynamic sitemap generation from content
- robots.ts : multi-bot rules with sitemap link
- layout.tsx : JSON-LD schema, GSC verification, manifest
- posts/page.tsx : per-page metadata + CollectionPage schema
Useful tools for validation after implementation:
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 35
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 StabilityNexus/StableViewpoints
-
documentation enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 57/100
StabilityNexus/StableViewpoints#105 · 1 comment ·
-
Dark Mode: Article title becomes invisible on hover inside Article CardsMay be free again @SOGeKING-NUL claimed this 352 days ago, and no pull request is open. Opengood first issue
StabilityNexus/StableViewpoints#29 · 11 comments · 1 assignee ·
All issues in StabilityNexus/StableViewpoints
Similar issues
-
[BUG]: Shared links drop the configured basePath on GitHub PagesPossibly taken @anshulchikhale30-p claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 comment ·
Maintainers usually reply within 1 day
-
Add: GTrekkerOpencheck:passed streams:add
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
Maintainers usually reply within 1 day
-
area: ui Bug Payload OSS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
payloadcms/payload#19839 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day