Skip to content

Free & Open-Source Invoice Generator - No Sign-Up, No Ads, Instant PDF Export, 100% In-Browser, and Fully Customizable Templates.

feat: SEO and footer improvements (#250)

Vlad Sazonau56ecc3db2964
diff --git a/.agents/skills/competitive-landscape/SKILL.md b/.agents/skills/competitive-landscape/SKILL.md
new file mode 100644
index 0000000..0883708
--- /dev/null
+++ b/.agents/skills/competitive-landscape/SKILL.md
@@ -0,0 +1,80 @@
+---
+name: competitive-landscape
+description: Map SEO market leaders, winning content themes, keyword coverage, backlinks, and strategic gaps.
+---
+
+# OpenSEO Competitive Landscape
+
+## Goal
+
+Answer: "Who is winning this SEO market, what content is working for them, and where are the openings?"
+
+Use this when the user wants a market-level view across several competitors. For a deep dive on one domain, use `competitor-analysis`.
+
+## Required inputs
+
+- `projectId`
+- Topic, seed keywords, market/category, or user's domain
+- Optional known competitors
+- Optional location/language
+
+## OpenSEO MCP tools
+
+- `research_keywords`: discover representative market queries.
+- `get_keyword_metrics`: validate known query sets with volume, difficulty, intent, and trends.
+- `get_serp_results`: identify recurring ranking domains across target queries.
+- `find_serp_competitors`: compare domains competing across supplied keywords; use this before manual SERP counting when a keyword set is available.
+- `get_domain_overview`: size organic footprint for candidate leaders.
+- `get_search_console_performance`: when the user's own domain is in the comparison and Search Console is connected, anchor their position with first-party clicks/impressions/CTR rather than third-party estimates.
+- `get_ranked_keywords`: find exact ranking keywords, URLs, ranks, intents, and SERP result types for leaders.
+- `get_backlinks_overview`: compare backlink/referring-domain strength where relevant.
+- `search_local_businesses`, `get_local_serp_results`, and `get_google_business_questions`: use for local SEO markets where proximity, Maps rankings, business categories, reviews, or Google Q&A affect who is winning.
+
+## Workflow
+
+1. Define the market query set:
+ - Use provided keywords, or call `research_keywords` to build 5-10 representative queries.
+ - Include mixed intent: informational, commercial, comparison, and tool/software terms when applicable.
+ - For local SEO, include neighborhood/city/service-area queries and identify the priority locations or coordinates.
+2. If the query set is already known, use `get_keyword_metrics` to validate relative demand and difficulty and `find_serp_competitors` to identify recurring domains at scale.
+3. For local SEO, call `search_local_businesses` and `get_local_serp_results` for the highest-priority location(s) before synthesizing winners. Use `get_serp_results` as a complement for organic pages, not as the only local evidence.
+4. Call `get_serp_results` for representative queries when live SERP composition, ranking URLs, or SERP features need inspection. Send at most 10 queries per call.
+5. Identify recurring domains and group them by type:
+ - Direct product competitors
+ - Publishers/media
+ - Marketplaces/directories
+ - Communities/forums
+ - Documentation/resources
+6. For the strongest recurring domains, call `get_domain_overview`; default to the top 3-5 domains before expanding.
+7. For direct competitors and relevant publishers, call `get_ranked_keywords`.
+8. Use `get_backlinks_overview` when backlink authority appears important or the user asks why a domain is winning. Backlinks may be unavailable if the account has not enabled that data; continue with SERP/domain evidence if it fails.
+9. Synthesize patterns: content types, themes, SERP formats, local-pack signals, authority advantages, and underserved angles.
+
+## Output format
+
+Start with the market read:
+
+- Market leaders
+- Most winnable opportunity area
+- Biggest barrier to ranking
+
+Then include:
+
+| Domain | Type | Why they matter | Organic footprint | Winning themes | Weakness/gap |
+| ------ | ---- | --------------- | ----------------- | -------------- | ------------ |
+
+Add:
+
+- Query set used
+- Content formats that are working
+- Keyword/theme gaps
+- Backlink or authority observations
+- Recommended next workflows: competitor analysis, keyword clustering, or content brief
+
+## Guardrails
+
+- Distinguish SEO competitors from business competitors.
+- Do not overstate exact traffic when OpenSEO returns estimates.
+- If using a small query set, call the result directional.
+- Do not assume a publisher is a product competitor; label domain types clearly.
+- For local markets, distinguish organic-page winners from Maps/local-pack winners.
diff --git a/.agents/skills/competitor-analysis/SKILL.md b/.agents/skills/competitor-analysis/SKILL.md
new file mode 100644
index 0000000..1ca9333
--- /dev/null
+++ b/.agents/skills/competitor-analysis/SKILL.md
@@ -0,0 +1,83 @@
+---
+name: competitor-analysis
+description: "Analyze one competitor's organic footprint, ranking keywords, content themes, backlinks, and gaps."
+---
+
+# OpenSEO Competitor Analysis
+
+## Goal
+
+Analyze one competitor deeply enough to decide what to learn from, avoid, counter-position against, or outrank.
+
+Use this for a named competitor. For identifying the market leaders first, use `competitive-landscape`.
+
+## Required inputs
+
+- `projectId`
+- Competitor domain
+- User's domain when comparison is requested
+- Optional topic/category/location/language
+
+## OpenSEO MCP tools
+
+- `get_domain_overview`: baseline organic traffic and keyword count.
+- `get_search_console_performance`: when comparing to the user's own domain and Search Console is connected, use it as the first-party baseline (real clicks/impressions/CTR/position) instead of estimating the user's own performance from third-party data.
+- `get_ranked_keywords`: exact keyword, URL, rank, intent, traffic, CPC, and SERP-type rows for the competitor domain or page.
+- `get_backlinks_overview`: backlink/referring-domain profile.
+- `find_serp_competitors`: validate whether the named competitor is a real search competitor across the target keyword set.
+- `search_local_businesses`, `get_local_serp_results`, and `get_google_business_questions`: use for local SEO competitors when Maps/local-pack visibility, nearby businesses, categories, or Google Q&A matter.
+- `get_serp_results`: validate direct head-to-head SERPs for important keywords.
+- `research_keywords`: expand gaps or category terms when needed.
+
+## Workflow
+
+1. Call `get_domain_overview` for the competitor, passing provided location/language when supported.
+2. If comparing to the user, call `get_domain_overview` for the user's domain too — and if Search Console is connected, `get_search_console_performance` for the user's real baseline.
+3. Call `get_ranked_keywords` for the competitor. Use filters like `maxRank`, `minSearchVolume`, `excludeBrandTerms`, and `resultTypes` to keep rows relevant.
+4. If comparing to the user, call `get_ranked_keywords` for the user's domain/page too, or use `get_serp_results` for the shared terms when a lighter check is enough.
+5. For local SEO, use `search_local_businesses` and `get_local_serp_results` around the relevant business location(s) before drawing local-pack conclusions. Add `get_google_business_questions` only when Q&A evidence matters.
+6. Use `find_serp_competitors` when the competitor was supplied by the user but its search overlap is unclear.
+7. Group competitor keywords into themes:
+ - Product/category terms
+ - Alternatives/comparisons
+ - Templates/tools/calculators
+ - Educational guides
+ - Branded demand
+ - Local/neighborhood terms when relevant
+8. Call `get_backlinks_overview` for the competitor, especially if authority appears to explain rankings. Continue without backlink evidence if it is unavailable.
+9. Use `get_serp_results` for important shared or target keywords to compare positioning, passing provided location/language when supported.
+10. Produce an actionable plan:
+ - What they are doing well
+ - Where they are vulnerable
+ - Which pages/keywords to pursue
+ - What to avoid copying
+
+## Output format
+
+Start with:
+
+- Competitor snapshot
+- Biggest lesson
+- Best opportunity to beat them
+
+Then include:
+
+| Area | Competitor pattern | Evidence | OpenSEO opportunity |
+| ---- | ------------------ | -------- | ------------------- |
+
+Include sections for:
+
+- Top keyword themes
+- Content/page types working for them
+- Backlink/authority notes
+- Head-to-head SERP observations
+- Priority actions for the user
+
+## Guardrails
+
+- Do not treat all competitor keywords as desirable. Filter for business fit.
+- Separate evidence from inference.
+- Do not infer competitor page/content-type patterns from keyword rows alone; use SERP or web evidence for page-level claims.
+- For local SEO, do not infer Maps/local-pack strength from national organic domain metrics alone; use local business and local SERP tools when the location is known or reasonably discoverable.
+- Do not recommend copying content; recommend a stronger angle or better answer to the same intent.
+- If the user's domain is unavailable, frame the analysis as competitor-only.
diff --git a/.agents/skills/keyword-clustering/SKILL.md b/.agents/skills/keyword-clustering/SKILL.md
new file mode 100644
index 0000000..0fbadf7
--- /dev/null
+++ b/.agents/skills/keyword-clustering/SKILL.md
@@ -0,0 +1,76 @@
+---
+name: keyword-clustering
+description: Cluster keywords by intent and map them to existing or proposed pages.
+---
+
+# OpenSEO Keyword Clustering
+
+## Goal
+
+Group keywords into page-level clusters and decide which existing or new page should target each cluster. This is a keyword mapping workflow, not just a semantic grouping exercise.
+
+## Required inputs
+
+- `projectId`
+- A keyword list, saved keyword tag, seed topic, or target domain
+- Optional existing URLs/pages to map against
+
+If keywords are not provided, use `list_saved_keywords` for saved sets, `research_keywords` for seed discovery, or `get_ranked_keywords` when the user starts from a target domain.
+
+## OpenSEO MCP tools
+
+- `list_saved_keywords`: fetch an existing keyword set, optionally filtered by tags.
+- `research_keywords`: expand a seed when the user starts from a topic.
+- `get_ranked_keywords`: gather exact ranking keywords and URLs when the user starts from a domain or page.
+- `get_search_console_performance`: when Search Console is connected, pull real queries with `dimensions: ["query","page"]` to map terms to the pages already earning impressions and to surface cannibalization (one query splitting clicks across multiple URLs).
+- `get_serp_results`: validate whether keywords belong on the same page by checking SERP overlap and intent.
+- `get_local_serp_results`: use for local SEO clusters when Maps/local-pack intent should affect page mapping.
+- `save_keywords`: optionally tag final clusters after user confirmation.
+
+## Workflow
+
+1. Gather the candidate keyword set.
+ - Use `get_search_console_performance` (dimensions `["query","page"]`) when Search Console is connected to start from real queries and the pages already ranking for them.
+ - Use `get_ranked_keywords` for domain/page-driven clustering.
+ - Use `search_local_businesses` and `get_local_serp_results` when proximity, local packs, or Google Business results determine whether terms belong on location pages.
+2. Remove duplicates, irrelevant terms, and terms that clearly require a different product or audience.
+3. Build clusters around intent and page type:
+ - Same SERP intent and similar ranking pages belong together.
+ - Different intent, buyer stage, or SERP format should be split.
+ - Similar words do not guarantee the same cluster.
+4. For important borderline terms, use a small `get_serp_results` batch to check overlap.
+5. Assign each cluster to:
+ - Existing URL, if supplied and appropriate
+ - New page recommendation, if no existing page fits
+ - Do-not-target / later bucket, if weak or off-strategy
+6. Identify cannibalization risk when multiple pages would target the same intent. When Search Console is connected, confirm it from real data with `get_search_console_performance` (`dimensions: ["query","page"]`) — the same query sending impressions to multiple URLs.
+7. Ask before applying cluster tags with `save_keywords`.
+
+## Output format
+
+Start with a short mapping summary:
+
+- Number of clusters
+- Pages to create
+- Existing pages to update
+- Cannibalization or consolidation issues
+
+Then include:
+
+| Cluster | Primary keyword | Secondary keywords | Intent | Target page | Priority | Notes |
+| ------- | --------------- | ------------------ | ------ | ----------- | -------- | ----- |
+
+For each cluster, include a recommended page brief:
+
+- Page type
+- Searcher problem
+- Required sections
+- Internal-link opportunities
+- Save/tag suggestion
+
+## Guardrails
+
+- Do not over-cluster tiny keyword sets. If there are fewer than 10 usable terms, produce a simple map.
+- Do not rely on lexical similarity alone. SERP intent wins.
+- Do not replace tags broadly without explicit confirmation.
+- If existing URL data is missing, label target pages as proposed.
diff --git a/.agents/skills/keyword-research/SKILL.md b/.agents/skills/keyword-research/SKILL.md
new file mode 100644
index 0000000..4bdfc40
--- /dev/null
+++ b/.agents/skills/keyword-research/SKILL.md
@@ -0,0 +1,70 @@
+---
+name: keyword-research
+description: "Discover keyword opportunities, evaluate metrics and SERPs, and save/tag promising terms."
+---
+
+# OpenSEO Keyword Research
+
+## Goal
+
+Turn seed topics into a prioritized keyword opportunity set using OpenSEO MCP data. The output should help the user decide what to target, what to save, and what to research next.
+
+## Required inputs
+
+- `projectId`
+- One or more seed topics, products, pages, competitors, or audience problems
+- Optional market/location/language
+
+If `projectId` is missing, use `list_projects` first. If the target market/location/language is unclear and would materially affect keyword metrics, ask the user; otherwise use the MCP tool defaults.
+
+## OpenSEO MCP tools
+
+- `research_keywords`: primary discovery tool. Use 1-5 seeds per call and prefer 150 results unless the user asks for exhaustive research.
+- `get_keyword_metrics`: hydrate up to 700 known keywords with volume, keyword difficulty (KD), search intent, CPC, and monthly trends in one call. Use it to score candidate or known terms — including the Search Console striking-distance queries from step 1.
+- `get_ranked_keywords`: pull exact ranking keyword rows when a target domain or page is part of the research brief.
+- `get_search_console_performance`: when Search Console is connected, start from the project's real first-party demand — queries already earning impressions and near-ranking ("striking distance") terms. Request a high `rowLimit` and filter average position 5-20 client-side, since the API sorts by clicks and can't filter by position. Then hydrate those striking-distance queries with `get_keyword_metrics` to attach difficulty and intent.
+- `get_serp_results`: inspect SERPs for the top candidate terms, especially when intent is ambiguous.
+- `search_local_businesses`, `get_local_serp_results`, and `get_google_business_questions`: use for local SEO topics when a business/location radius matters.
+- `list_saved_keywords`: avoid duplicating already-saved work or use existing tags as context.
+- `save_keywords`: save selected keywords only after explicit user confirmation.
+
+## Workflow
+
+1. Normalize seeds into a small set of distinct research angles. If Search Console is connected for the project, first pull `get_search_console_performance` (high `rowLimit`, default lookback), filter to striking-distance positions (~5–20) client-side, and hydrate those queries with `get_keyword_metrics` to attach KD and intent. That ranked, hydrated list is your fastest opportunity set — work it before broad discovery.
+2. If the request is local SEO, identify the business, location/coordinates or service area, and local categories. Use `search_local_businesses` and `get_local_serp_results` for the most important location/keyword set instead of relying only on national keyword/SERP data.
+3. Call `research_keywords` for exploratory seeds. Use bulk calls when possible.
+4. Use `get_keyword_metrics` to hydrate a fixed keyword list — or the striking-distance queries from step 1 — with volume, KD, and intent before prioritizing.
+5. Use `get_ranked_keywords` when the user provides a domain/page and wants opportunities based on current rankings, near-misses, or competitor-owned terms.
+6. Remove irrelevant, duplicate, branded-only, and off-intent terms.
+7. Prioritize by practical opportunity, not volume alone:
+ - Strong match to the user's product/page/topic
+ - Clear search intent
+ - Reasonable difficulty
+ - Useful volume/CPC signal
+ - SERP where the user can plausibly compete
+ - For local SEO, local-pack/Maps visibility and proximity fit
+8. Use `get_serp_results` for high-potential or ambiguous keywords when SERP intent would change the recommendation; keep the default check small.
+9. Present a shortlist and a longer opportunity table.
+10. Ask before saving keywords. When saving, suggest concise tags such as `topic:<topic>`, `intent:<intent>`, or `page:<slug>`.
+
+## Output format
+
+Start with the highest-signal recommendation:
+
+- Best opportunity theme
+- Top keywords to target now
+- Keywords to save
+- Risks or SERP caveats
+
+Then include a compact table:
+
+| Keyword | Intent | Volume | KD | CPC | Priority | Notes |
+| ------- | ------ | -----: | --: | --: | -------- | ----- |
+
+End with next actions, including whether to run keyword clustering, create a content brief, or save the chosen keywords.
+
+## Guardrails
+
+- Do not invent metrics. If OpenSEO does not return a value, write `unknown`.
+- Do not call `save_keywords` without explicit confirmation.
+- Prefer business-fit and intent-fit over chasing the largest volume term.
diff --git a/.agents/skills/link-prospecting/SKILL.md b/.agents/skills/link-prospecting/SKILL.md
new file mode 100644
index 0000000..e9b9fb7
--- /dev/null
+++ b/.agents/skills/link-prospecting/SKILL.md
@@ -0,0 +1,107 @@
+---
+name: link-prospecting
+description: Find link prospects, discover contact paths, and draft outreach from SERPs and backlink signals.
+---
+
+# OpenSEO Link Prospecting
+
+## Goal
+
+Find realistic pages, sites, and authors that might reference the user's page, product, study, guide, or tool. Use OpenSEO for prospect discovery, then use available web/search/browser tools for contact discovery.
+
+## Required inputs
+
+- `projectId`
+- User domain or target URL
+- Linkable asset, page, product, study, tool, or topic
+- Optional competitors
+- Optional market/location/language
+
+## OpenSEO MCP tools
+
+- `get_serp_results`: find ranking articles, listicles, resource pages, comparisons, and topical publishers.
+- `get_backlinks_overview`: inspect competitor domain or page backlink/referring-domain patterns.
+- `get_domain_overview`: qualify important prospect domains.
+- `get_ranked_keywords`: understand what a prospect or competitor ranks for when topical fit matters.
+- `search_local_businesses` and `get_local_serp_results`: use for local SEO link prospecting when nearby businesses, local competitors, or Maps/category signals can reveal partnership targets.
+- `research_keywords`: expand prospecting queries.
+
+## Contact discovery tools
+
+After OpenSEO identifies good prospects, use available non-OpenSEO browsing or search tools for public contact discovery. Depending on the client, this may be web search, page fetches, browser automation, or a search API.
+
+Look for:
+
+- Author byline pages
+- Contact pages
+- Editorial guidelines
+- About/team pages
+- LinkedIn, X, Bluesky, or other professional profiles
+- Newsletter or publication masthead pages
+- Public email addresses in page HTML or visible page text
+- Structured data such as `Person`, `Organization`, `sameAs`, or `email`
+
+Only record contact details that were actually found. Include the source URL for any email, profile, or contact form.
+
+## Prospecting query patterns
+
+Build queries from the asset/topic:
+
+- `<topic> resources`
+- `best <category> tools`
+- `<competitor> alternatives`
+- `<topic> statistics`
+- `<topic> guide`
+- `<topic> examples`
+- `<topic> templates`
+- `<topic> software`
+- `<topic> for <audience>`
+
+Use `get_serp_results` in batches for the most relevant patterns. Send at most 10 queries per call.
+
+## Workflow
+
+1. Clarify the linkable asset and the reason someone would reference it.
+2. Build 5-10 prospecting queries by default.
+3. Call `get_serp_results` for those queries.
+4. If competitors are provided, call `get_backlinks_overview` for the strongest competitor domains or pages first. Continue without backlink evidence if it is unavailable.
+5. For local SEO, use `search_local_businesses` and `get_local_serp_results` around priority locations to identify nearby competitors, categories, and local SERP evidence before searching for local chambers, associations, campus resources, community pages, and directories.
+6. Filter prospects:
+ - Keep topical relevance and editorial pages.
+ - Prioritize articles, directories, resource pages, comparisons, statistics pages, templates, and curated lists.
+ - Deprioritize homepages, login pages, thin affiliate pages, spam, unrelated forums, and direct competitors unless a comparison angle is valid.
+7. For each good prospect, define the outreach angle:
+ - Broken/missing resource
+ - Better current data
+ - Useful tool/template
+ - Alternative or comparison inclusion
+ - Expert quote or supporting reference
+8. For the strongest prospects, visit or search the prospect site to find the best contact path.
+9. Draft outreach messages. If contact details were found, include the source. If not, list the next best contact-discovery path.
+
+## Output format
+
+Start with:
+
+- Best outreach angle
+- Highest-priority prospect type
+- Any data limitations
+
+Then include:
+
+| Prospect URL | Site/domain | Source | Relevance | Suggested angle | Contact path | Priority |
+| ------------ | ----------- | ------ | --------- | --------------- | ------------ | -------- |
+
+Then provide 2-3 reusable outreach drafts:
+
+- Resource/list inclusion
+- Article update/reference suggestion
+- Competitor alternative/comparison angle
+
+## Guardrails
+
+- Do not invent email addresses, social handles, or contact names.
+- Do not say OpenSEO found contact details unless an OpenSEO tool returned them. Attribute contact discovery to the web/search/browser source used.
+- If contact details are not available after a reasonable search, recommend specific discovery steps such as checking the author page, contact page, LinkedIn, X, or a reputable contact-enrichment tool.
+- Avoid spammy mass outreach. Personalize by page and reason.
+- Flag prospects that are direct competitors or likely paid placements.
diff --git a/.agents/skills/merge-ready/SKILL.md b/.agents/skills/merge-ready/SKILL.md
new file mode 100644
index 0000000..1c5e547
--- /dev/null
+++ b/.agents/skills/merge-ready/SKILL.md
@@ -0,0 +1,69 @@
+---
+name: merge-ready
+description: Take a branch from "code exists (or is about to)" to "ready for Ben's final review" — multi-axis subagent review with verified findings, fixes, ci:check, checkpoint commits, and an updated PR. Use whenever the user says a feature/fix/branch should be "merge ready", asks to get changes ready for review, or appends this to a build request ("build X and make it merge-ready").
+---
+
+# Merge ready
+
+Drive the current work to the point where the only remaining step is Ben's own review and merge. The deliverable is a pushed branch with a clean `pnpm ci:check`, checkpoint commits along the way, and an open PR with a high-level description plus review instructions.
+
+**Never merge the PR. Ben always reviews last.**
+
+## 0. Figure out the starting point
+
+This skill composes with feature work — it is not only a review pass:
+
+- **Invoked alongside a build request** ("build X, make it merge-ready"): implement the feature/fix first, committing as you go, then continue below. The review phases cover _all_ changes on the branch vs `origin/main`, not just the last edit.
+- **Invoked on existing work** ("make this branch merge-ready"): start directly at step 1. The scope is `git diff origin/main...HEAD` plus anything uncommitted.
+
+## 1. Sync with main
+
+- `git fetch origin main`. If the branch is behind, merge `origin/main` in and resolve conflicts (favor main's version for code this branch didn't intentionally change).
+- **Checkpoint:** commit the merge before starting review, so conflict resolution is auditable separately from review fixes.
+
+## 2. Multi-axis subagent review
+
+Spawn independent review subagents **in parallel**, one per axis, each given repo access and the complete branch scope:
+
+- committed changes: `git diff origin/main...HEAD`
+- staged changes: `git diff --cached`
+- unstaged changes: `git diff`
+- untracked files: `git status --short`, followed by reading every in-scope untracked file
+
+Do not let an uncommitted or newly created file escape review merely because it is absent from `origin/main...HEAD`.
+
+1. **Unnecessary complexity** — thin wrappers, needless indirection, single-use abstractions, defensive guards for impossible states, dead config. This codebase deliberately stays simple.
+2. **Security** — authz on new endpoints (org/project scoping), SSRF, injection, secrets handling, anything user-input-shaped reaching D1/R2/external APIs.
+3. **Billing & metering** — ways a user could trigger DataForSEO/provider spend without being metered, charged-but-failed paths, retry/loop amplification, endpoints with unexpectedly high per-call user cost. Credits are billed via Autumn; uncounted spend is a revenue leak.
+4. **Library & project idioms** — TanStack (Router/Query/Start) used idiomatically; patterns match how the rest of the codebase already does it (shared application/provider error boundaries, db/schema conventions, existing component patterns). Flag novel patterns where an established one exists.
+5. **Vibe-coded cruft** — leftover scaffolding, stale comments narrating the edit history, console.logs, TODO-without-owner, copy-pasted near-duplicates, files/exports nothing uses.
+
+Each reviewer returns findings with file:line, severity (`blocker` / `should-fix` / `nitpick`), and a one-line rationale. Tell reviewers explicitly: this is an early-stage product — do not chase theoretical edge cases; mark anything debatable as `nitpick`.
+
+## 3. Verify findings — never blindly accept
+
+For each `blocker` and `should-fix` finding, spawn verification subagents (in parallel) that adversarially check the finding against the actual code and verdict **APPLY / APPLY-MODIFIED / REJECT** with reasoning. Drop rejected findings. Nitpicks don't need verification — they're reported, not necessarily fixed.
+
+### Preserve review learnings
+
+After verification, route durable learnings without forcing every review to change policy:
+
+- If an **APPLY** or **APPLY-MODIFIED** finding reveals a recurring or high-risk repository invariant that existing `.greptile/` context and CI do not capture, use `maintain-greptile-rules` and apply its promotion bar.
+- Keep one-off bugs as code fixes and regression tests. Put deterministic mechanical checks in CI or lint instead of Greptile.
+- When a small tooling, documentation, or workflow frustration occurs, use `papercuts` to append it to `.agents/PAPERCUTS.md`; do not derail merge-ready work to fix it.
+
+## 4. Fix, check, loop
+
+- Apply verified `blocker`/`should-fix` fixes. Apply nitpicks only when trivial and clearly right; otherwise list them in the PR for Ben to judge.
+- **Checkpoint:** commit fixes in logical groups (e.g. one commit per axis or per concern) so the fix history is reviewable on its own.
+- Run `pnpm ci:check` (prettier, knip, tsc, oxlint). Fix failures and re-run until clean. If a fix was substantial (not formatting/lint), run a quick re-review of just that change.
+- Loop until ci:check passes and no verified findings remain unaddressed.
+
+## 5. Push and open/update the PR
+
+- Push the branch. Open a PR against `main` if one doesn't exist; otherwise update the existing PR's description.
+- PR description requirements:
+ - **High-level** — what changed and why, written for a human skimming. No file paths, no per-file changelog.
+ - **How to review** — a short ordered guide: what to look at first, what the risky/judgment-call areas are, what was deliberately left out of scope.
+ - **Review notes** — unfixed nitpicks and any REJECT verdicts worth a second opinion, clearly labeled as such.
+- Report back to Ben: PR link, one-paragraph summary, and anything that still needs his judgment. Do not merge.
diff --git a/.agents/skills/openseo-release-notes/SKILL.md b/.agents/skills/openseo-release-notes/SKILL.md
new file mode 100644
index 0000000..4a1252d
--- /dev/null
+++ b/.agents/skills/openseo-release-notes/SKILL.md
@@ -0,0 +1,68 @@
+---
+name: openseo-release-notes
+description: 'Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.'
+---
+
+# OpenSEO release notes
+
+Cut a release for this repo end to end. The deliverables are a version bump in `package.json`, a new `release-notes/v<version>.md`, and a PR against `origin/main` titled `release: v<version>`.
+
+## 1. Bump the version
+
+- Read `package.json`. If the branch has already bumped `version`, treat that as the source of truth and do not change it.
+- Otherwise bump the patch version (e.g. `0.0.19` → `0.0.20`). Only bump minor/major if explicitly asked.
+
+## 2. Collect the changes since the last release
+
+- Find the latest tag: `git tag --sort=-creatordate | head -1`. Verify the branch is up to date with `origin/main` (`git fetch origin main && git log HEAD..origin/main --oneline` should be empty; flag it if not).
+- List commits: `git log <last-tag>..HEAD --oneline`. You can also run `pnpm release:notes` for a raw commit inventory — use it only as a checklist of candidate changes, never as the draft's structure (its Improved/Changed/Docs sections must not appear in the notes).
+- For each commit, fetch the PR body and author (`gh pr view <num> --repo <repo> --json title,body,author`) — squash-commit subjects can be stale. The `(#NN)` in commit subjects can reference **either** repo: try `bensenescu/open-seo` (origin) first and fall back to `every-app/open-seo` (public) — outside contributors' PRs and their handles live on the public repo. Commits with no `(#NN)` may still be an outside contribution with a public PR (`gh pr list --repo every-app/open-seo --state merged --author <login>`); check `git log --format=%an` for the author. Verify claims against the final code when a PR body and commit subject disagree (features get reverted before merge).
+- Record the PR author's GitHub handle alongside each change so the bullet can credit them.
+
+## 3. Draft the notes
+
+Write `release-notes/v<version>.md`. **`release-notes/v0.0.24.md` is the canonical style exemplar** — match it (v0.0.25 and later follow the same style); v0.0.23 and earlier are the old verbose style, never imitate them. The notes are a scannable digest, not documentation: the whole file fits on one screen (roughly 15 lines including headings), and every line earns its place.
+
+Format:
+
+- Top line: a fragment naming the release's 2–3 highlights ("GSC UI, improved app layout and beta in app agent."). Not a "This release brings…" sentence.
+- Sections: `## What's new` and `## Fixed` only. There is no "Improved" section — an improvement is either headline-worthy (What's new) or it's cut.
+- **What's new bullets name the feature; they don't sell it.** One short line each ("Redesigned the app layout", "Get GSC Insights inside the app") — no em-dash feature tours, no "so you can…" benefit copy, no lists of everything the feature touches. If the name alone is ambiguous, one clause of plain-words context is the maximum.
+- At most **one sub-bullet per feature**, one short line: the single most useful detail, a requirement ("Requires `OPENROUTER_API_KEY`"), or an expectation-setter.
+- **Label rough features "(Beta)"** and set expectations honestly, including pointing at the better alternative for now. The expectation-setter rides the top-level line after a dash ("(Beta) In app agent - MCP is still recommended, but we'll be working to improve this during the summer."), keeping the sub-bullet slot free for a requirement or detail.
+- Fixed: 3–5 bullets, one plain sentence each, only bugs a user plausibly hit and would recognize ("Claude answers in AI search work again."). No error codes, status codes, schema/infra vocabulary, or mechanism. If more than four qualify, keep the ones hit in core flows (searches, audits, tracking, MCP answers) and drop fixes for recovering self-inflicted state (re-adding, un-archiving, refreshing) first.
+- **Credit the contributor.** End the bullet with `— thanks @handle` for outside contributors only — never for the maintainer's own PRs (`bensenescu`). Credit goes on the top-level bullet, not sub-bullets. Multiple contributors: `— thanks @a, @b`.
+- End with: `Full Changelog: https://github.com/every-app/open-seo/compare/v<prev>...v<version>`
+
+Curation — this is where the work is. Cut aggressively; the Full Changelog link covers the long tail:
+
+- Only changes to the **product itself** — the app, the MCP tools, the SEO data/features someone running OpenSEO actually uses. Litmus test per bullet: **would a self-hoster notice this while using the product?** Caring in the abstract (a new backend option, a raised cap) is not enough.
+- Do NOT mention:
+ - **Marketing-website (`web/`) changes** — landing pages, copy, positioning, blog.
+ - **Pricing / plans / subscription / billing** — paywalls, free-trial/plan changes, Autumn config. Hosted-commercial concerns, irrelevant to self-hosters.
+ - **Onboarding-flow-only changes** — signup/onboarding chat, profiling steps, upgrade rails, email-verification UX. Not a product capability, even when sizable.
+ - **Hosted-app internals & meta** — analytics, specs/ADRs, CI, refactors, dependency bumps.
+ - **Invisible-to-the-user work, even when product-relevant** — security hardening, raised caps/limits, stability/memory/perf fixes, database/backend options and migrations. A user reading the notes should recognize every line from using the product; if they'd only notice it in a config file or an incident that no longer happens, cut it.
+- When torn between including and cutting, cut. A 4-bullet What's new that gets read beats a 10-bullet one that doesn't.
+- Never invent features — every claim must trace to a commit.
+- Numbers in bullets are usually selling — cut them; if one is genuinely load-bearing, quote the conservative, typical figure, never a cherry-picked best case.
+
+## 4. Review and verify
+
+1. Spawn a reviewer subagent with: the draft, the guidelines above, the per-commit facts you gathered, and repo access. It returns numbered review comments citing which guideline each violates. Its charge includes **verbosity**: flag any bullet that sells instead of names, any second sub-bullet, any Fixed bullet with mechanism vocabulary, and anything that pushes the file past one screen.
+2. For each substantive comment, spawn a verification subagent (in parallel) that adversarially checks the comment against the actual commits/code and verdicts APPLY / APPLY-MODIFIED / REJECT.
+3. Apply only verified comments.
+
+## 5. Open the PR
+
+- Commit the version bump, release notes, and any skill changes on a branch named `claude/v<version>` (use the current branch if it already follows this pattern).
+- Push to `origin` and open a PR against `main` titled exactly `release: v<version>`. PR body: the release notes content.
+- Do not tag or publish the GitHub release — that happens after merge. After merge, run `pnpm release:publish`. It reads the version from `package.json` and publishes the matching `release-notes/v<version>.md` to `every-app/open-seo`.
+- The equivalent command is:
+
+ ```sh
+ gh release create v<version> \
+ --repo every-app/open-seo \
+ --title v<version> \
+ --notes-file release-notes/v<version>.md
+ ```
diff --git a/.agents/skills/seo-coach/SKILL.md b/.agents/skills/seo-coach/SKILL.md
new file mode 100644
index 0000000..8688416
--- /dev/null
+++ b/.agents/skills/seo-coach/SKILL.md
@@ -0,0 +1,107 @@
+---
+name: seo-coach
+description: Enter a friendly OpenSEO coach mode that explains workflows, recommends next steps, and helps users use agents, web search, scraping, and MCP data effectively.
+---
+
+# OpenSEO Coach
+
+## Goal
+
+Act as a friendly SEO coach for users working with OpenSEO and an AI agent. Help them understand what the workflows do, choose the right next action, and use the agent's full toolset effectively.
+
+## Tone
+
+Be warm, direct, and beginner-friendly. Ask whether the user is new to SEO and adapt the explanation depth. Avoid sounding like a course or a consultant deck. Make SEO feel doable.
+
+## First response
+
+When this mode starts, orient the user:
+
+- Ask whether they are new to SEO, experienced, or somewhere in between.
+- Ask what site or project they are working on.
+- Ask whether they want strategy, execution help, or explanation of the tools.
+- Offer 2-4 concrete next options, not a long menu.
+
+Example:
+
+```text
+I can coach you through this. Are you new to SEO, or do you mostly want help using OpenSEO faster?
+
+Good starting points:
+- Set up SEO project context
+- Find keyword opportunities
+- Map keywords to pages
+- Study a competitor
+- Build link prospects for a page
+```
+
+## What each workflow does
+
+- `seo-project-setup`: sets up the workspace, verifies MCP, captures goals and positioning, and connects Google Search Console (or imports GSC exports).
+- `keyword-research`: finds search opportunities from seed topics and evaluates volume, difficulty, CPC, intent, and SERPs.
+- `keyword-clustering`: groups keywords by intent and maps clusters to existing or proposed pages.
+- `competitive-landscape`: identifies who wins across a market and what content/backlink patterns are working.
+- `competitor-analysis`: studies one competitor's keywords, content themes, backlink profile, and gaps.
+- `link-prospecting`: finds likely link opportunities, discovers contact paths, and drafts outreach.
+
+## Tool coaching
+
+Explain the difference between data sources:
+
+- OpenSEO MCP tools provide SEO data such as keyword research, exact ranked keywords, search volume, SERPs, SERP competitors, local business and Maps data, domain overviews, backlinks, saved keywords, projects, and rank trackers.
+- Google Search Console (when connected on the project's Integrations page) is the user's own first-party data — real clicks, impressions, CTR, and position. Read it live with `get_search_console_performance` instead of asking for CSV exports. It's free (no credits) and the best starting point for "what already ranks" and near-ranking opportunities.
+- Web search can find current market context, recent pages, reviews, docs, social profiles, and contact paths outside OpenSEO.
+- Browser/page scraping can extract page copy, headings, author names, contact links, schema, and content structure.
+- Local files can preserve strategy, GSC CSVs, content briefs, crawls, prospect lists, and prior decisions over time.
+
+Encourage the user to put project files in one SEO folder so the agent can reuse context.
+
+## Coaching patterns
+
+When the user is unsure what to do:
+
+1. Clarify their goal.
+2. Identify what data they already have.
+3. Pick one workflow.
+4. Explain what the agent will do.
+5. Ask for only the next needed input.
+
+When the user asks for education:
+
+- Explain the concept plainly.
+- Show how it maps to an OpenSEO workflow.
+- Give a concrete example.
+- Offer to run the next step.
+
+When the user asks for strategy:
+
+- Anchor on business goals and positioning before keywords.
+- Separate SEO competitors from business competitors.
+- Prioritize pages and topics that can plausibly create business value.
+- Use SERPs to understand intent instead of guessing.
+- For local SEO, use local visibility/Maps evidence instead of relying only on national keyword and organic-domain metrics.
+
+When the user asks for execution:
+
+- Move quickly into the relevant workflow.
+- Use OpenSEO MCP data where available.
+- Use web/search/browser tools for context that OpenSEO does not provide.
+- Save or tag data only after confirmation.
+
+## Suggested next actions
+
+Offer concise options based on context:
+
+- "Let's set up project context first."
+- "Let's research keywords from your seed topics."
+- "Let's cluster your GSC/query export into page targets."
+- "Let's map the competitive landscape before choosing pages."
+- "Let's study one competitor."
+- "Let's find link prospects for your best linkable asset."
+
+## Guardrails
+
+- Do not overload beginners with every SEO concept at once.
+- Do not pretend OpenSEO MCP can browse arbitrary pages or discover contacts by itself.
+- Distinguish live SEO data, web evidence, local-file evidence, and coaching judgment.
+- Keep recommendations actionable: one next step is usually better than ten.
diff --git a/.agents/skills/seo-project-setup/SKILL.md b/.agents/skills/seo-project-setup/SKILL.md
new file mode 100644
index 0000000..9101f14
--- /dev/null
+++ b/.agents/skills/seo-project-setup/SKILL.md
@@ -0,0 +1,165 @@
+---
+name: seo-project-setup
+description: Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.
+---
+
+# OpenSEO SEO Project Setup
+
+## Goal
+
+Help the user set up a local SEO workspace for one website or SEO project. The folder is where the agent saves notes, goals, exports, briefs, reports, preferences, and project context over time. This is a workspace and context setup workflow, not a full audit.
+
+## Tone
+
+Be friendly, practical, and structured. Ask questions in small batches. Explain why each item matters only when useful. Do not overwhelm a beginner with jargon.
+
+## Checklist
+
+### 1. Pick a working folder
+
+Suggest that the user choose or create a local folder for SEO work, for example:
+
+- `~/SEO/<company-or-site>/`
+- `~/Documents/SEO/<company-or-site>/`
+- A repo or workspace folder if SEO work should live beside website/content files
+
+Explain that keeping notes, exports, briefs, scraped pages, reports, and preferences in one folder helps the agent build context over time. Future SEO workflows can use that folder rather than starting from a blank conversation.
+
+Recommended starter structure:
+
+```text
+seo-workspace/
+ README.md
+ gsc/
+ keywords/
+ competitors/
+ content/
+ outreach/
+ reports/
+```
+
+Do not create folders unless the user asks. If file tools are available and the user asks, create a simple structure and a short `README.md` with the current goals, known sites, and user preferences for how the agent should approach SEO for this project.
+
+### 2. Collect website scope
+
+Ask for:
+
+- Primary website/domain
+- Additional domains or subdomains
+- Important products, services, categories, or pages
+- Target countries/languages
+- Whether the site is new, established, migrating, or recovering from a drop
+- CMS or publishing workflow, if relevant
+
+### 3. Capture goals
+
+Ask the user what they want from SEO:
+
+- More qualified leads
+- More signups/trials
+- More ecommerce revenue
+- More newsletter/audience growth
+- More brand/category awareness
+- Recovery from traffic loss
+- Better ranking for specific pages
+
+Ask for success metrics and timeframe. If goals are vague, help turn them into measurable goals such as "increase non-branded organic signups" or "rank top 10 for 20 buying-intent terms."
+
+### 4. Capture positioning and strategy context
+
+Ask what research they have already done about the company, product, audience, and competitors. Request any notes, docs, customer interviews, positioning docs, pitch decks, landing pages, or strategy memos they can share.
+
+Probe for:
+
+- Who the product or site is for
+- What pain it solves
+- Why users choose it over alternatives
+- Competitors and substitutes
+- Strong opinions or positioning claims
+- Best customers and bad-fit customers
+- Existing content that already converts
+- Topics they do not want to target
+
+If the user has not done this yet, offer to help research positioning using the company website, competitor pages, reviews, forums, and web search.
+
+### 5. Verify OpenSEO MCP
+
+After the user has described the company, website, goals, and positioning, check that OpenSEO MCP is configured and mapped to the right project:
+
+1. Use `whoami` if available.
+2. Use `list_projects` to confirm the user can access projects.
+3. Match the project to the website/domain they want to rank for.
+4. If the project list is ambiguous, ask the user which project should be used.
+5. If the MCP is unavailable, tell the user to connect OpenSEO MCP before continuing with live OpenSEO data.
+
+Do not run research tools just to test connectivity; `whoami` and `list_projects` are enough.
+
+### 6. Connect Google Search Console
+
+GSC is the richest first-party signal: existing impressions, near-ranking terms, cannibalization, and pages that already have search demand.
+
+**Preferred (hosted): connect it natively.** On the project's Integrations page, connect Google Search Console and pull live data with `get_search_console_performance`. Once connected, the agent reads it directly in `keyword-research` and `keyword-clustering` — no manual files to maintain.
+
+**Fallback (self-hosted, or if the user prefers files):** ask the user to export CSVs from Search Console into the SEO working folder.
+
+Recommended exports:
+
+- Queries: last 3 months and last 16 months if available
+- Pages: last 3 months and last 16 months if available
+- Query + page combinations when possible
+- Countries/devices if relevant
+
+Ask them to drop files into `gsc/` and use names like:
+
+```text
+gsc/queries-last-3-months.csv
+gsc/pages-last-3-months.csv
+gsc/queries-last-16-months.csv
+gsc/pages-last-16-months.csv
+```
+
+### 7. Inventory existing assets
+
+Ask for or discover:
+
+- Sitemap or important URL list
+- Current blog/resources/content library
+- Product/category/feature pages
+- Existing keyword lists
+- Current rank trackers
+- Backlink or PR assets
+- Linkable assets such as studies, templates, tools, datasets, calculators, or original opinions
+
+### 8. Recommend first workflow
+
+After intake, recommend one next OpenSEO workflow:
+
+- `keyword-research`: when the user needs ideas from seed topics
+- `keyword-clustering`: when they have keywords or GSC data to map to pages
+- `competitive-landscape`: when the market is unclear
+- `competitor-analysis`: when they know a competitor to study
+- `link-prospecting`: when they have a linkable asset or target page
+
+## Output format
+
+Use a checklist with statuses:
+
+| Step | Status | Notes | Next action |
+| ---- | ------ | ----- | ----------- |
+
+Then summarize:
+
+- Working folder
+- OpenSEO MCP/project status
+- Sites in scope
+- Goals
+- Known positioning
+- Uploaded data/files
+- Recommended next workflow
+
+## Guardrails
+
+- Keep setup lightweight. The user should feel oriented, not assigned homework.
+- Do not pretend a GSC CSV has been uploaded unless you can see it, and do not claim Search Console is connected unless `get_search_console_performance` confirms it (it returns a "not connected" message otherwise).
+- Keep project setup focused on setup and context unless the user asks for live research.
+- If web search or scraping is used for positioning research, distinguish source evidence from inference.
diff --git a/e2e/about.test.ts b/e2e/about.test.ts
index af28910..774942b 100644
--- a/e2e/about.test.ts
+++ b/e2e/about.test.ts
@@ -6,6 +6,10 @@ import {
TWITTER_URL,
VIDEO_DEMO_FALLBACK_IMG,
} from "@/config";
+import {
+ LANGUAGE_TO_NATIVE_LABEL,
+ SUPPORTED_LANGUAGES,
+} from "@/app/schema";
import { expect, test } from "@playwright/test";
test.describe("About page", () => {
@@ -441,7 +445,7 @@ test.describe("About page", () => {
await page
.getByRole("button", { name: "Switch language", exact: true })
.click();
- await page.getByText("Français").click();
+ await page.getByRole("menuitem", { name: "Français" }).click();
await expect(page).toHaveURL("/fr/about");
@@ -455,6 +459,55 @@ test.describe("About page", () => {
).toBeVisible();
});
+ test("should display footer about language links", async ({ page }) => {
+ await page.goto("/en/about");
+
+ const footer = page.getByRole("contentinfo");
+ const footerAboutLinks = footer.getByTestId("footer-about-links");
+
+ await expect(
+ footerAboutLinks.getByRole("heading", {
+ level: 3,
+ name: "About EasyInvoicePDF",
+ exact: true,
+ }),
+ ).toBeVisible();
+
+ for (const lang of SUPPORTED_LANGUAGES) {
+ const link = footerAboutLinks.getByRole("link", {
+ name: LANGUAGE_TO_NATIVE_LABEL[lang],
+ exact: true,
+ });
+
+ await expect(link).toBeVisible();
+ await expect(link).toHaveAttribute("href", `/${lang}/about`);
+ await expect(link).not.toHaveAttribute("target", "_blank");
+ }
+ });
+
+ test("should navigate to localized about page from footer language link", async ({
+ page,
+ }) => {
+ await page.goto("/en/about");
+
+ const footerAboutLinks = page
+ .getByRole("contentinfo")
+ .getByTestId("footer-about-links");
+
+ await footerAboutLinks
+ .getByRole("link", { name: "Français", exact: true })
+ .click();
+
+ await expect(page).toHaveURL("/fr/about");
+
+ await expect(
+ page.getByRole("banner").getByRole("link", {
+ name: "Ouvrir",
+ exact: true,
+ }),
+ ).toBeVisible();
+ });
+
test("should navigate to app when clicking Go to App button", async ({
page,
}) => {
diff --git a/messages/de.json b/messages/de.json
index 21e7fac..1d3a064 100644
--- a/messages/de.json
+++ b/messages/de.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Ein kostenloses Open-Source-Tool zur Erstellung professioneller PDF-Rechnungen mit Live-Vorschau.<br></br><br></br>Keine Buchhaltungssoftware. Keine Compliance-Garantien. Durch die Nutzung dieses Tools stimmen Sie den <tosLink>Nutzungsbedingungen</tosLink> zu.",
"headings": {
+ "about": "Über EasyInvoicePDF",
+ "solutions": "Lösungen",
"product": "Produkt",
"company": "Unternehmen",
"community": "Community"
diff --git a/messages/en.json b/messages/en.json
index 6c9e8f7..1d2314a 100644
--- a/messages/en.json
+++ b/messages/en.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Create professional invoices in seconds with our free & open-source invoice maker. 100% in-browser, no sign-up required. Includes live PDF preview and a Stripe-style template - perfect for freelancers, startups, and small businesses.<br></br><br></br>Not accounting software. No compliance guarantees. By using this tool, you agree to the <tosLink>Terms of Service</tosLink>.",
"headings": {
+ "about": "About EasyInvoicePDF",
+ "solutions": "Solutions",
"product": "Product",
"company": "Company",
"community": "Community"
diff --git a/messages/es.json b/messages/es.json
index 3361267..64acac8 100644
--- a/messages/es.json
+++ b/messages/es.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Una herramienta gratuita de código abierto para crear facturas PDF profesionales con vista previa en tiempo real.<br></br><br></br>No es software de contabilidad. Sin garantías de cumplimiento. Al usar esta herramienta, aceptas los <tosLink>Términos del servicio</tosLink>.",
"headings": {
+ "about": "Sobre EasyInvoicePDF",
+ "solutions": "Soluciones",
"product": "Producto",
"company": "Empresa",
"community": "Comunidad"
diff --git a/messages/fr.json b/messages/fr.json
index 4d90151..ef929c3 100644
--- a/messages/fr.json
+++ b/messages/fr.json
@@ -49,6 +49,8 @@
"footer": {
"description": "Un outil gratuit et open-source pour créer des factures PDF professionnelles avec aperçu en temps réel.<br></br><br></br>Pas un logiciel de comptabilité. Aucune garantie de conformité. En utilisant cet outil, vous acceptez les <tosLink>Conditions d'utilisation</tosLink>.",
"headings": {
+ "about": "À propos d'EasyInvoicePDF",
+ "solutions": "Solutions",
"product": "Produit",
"company": "Entreprise",
"community": "Communauté"
diff --git a/messages/it.json b/messages/it.json
index c054253..40fb1c7 100644
--- a/messages/it.json
+++ b/messages/it.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Uno strumento gratuito e open-source per creare fatture PDF professionali con anteprima in tempo reale.<br></br><br></br>Non è un software di contabilità. Nessuna garanzia di conformità. Utilizzando questo strumento, accetti i <tosLink>Termini di servizio</tosLink>.",
"headings": {
+ "about": "Informazioni su EasyInvoicePDF",
+ "solutions": "Soluzioni",
"product": "Prodotto",
"company": "Azienda",
"community": "Community"
diff --git a/messages/nl.json b/messages/nl.json
index 494b040..69dfda6 100644
--- a/messages/nl.json
+++ b/messages/nl.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Een gratis, open-source tool voor het maken van professionele PDF-facturen met realtime voorbeeld.<br></br><br></br>Geen boekhoudsoftware. Geen nalevingsgaranties. Door deze tool te gebruiken, gaat u akkoord met de <tosLink>Servicevoorwaarden</tosLink>.",
"headings": {
+ "about": "Over EasyInvoicePDF",
+ "solutions": "Oplossingen",
"product": "Product",
"company": "Bedrijf",
"community": "Community"
diff --git a/messages/pl.json b/messages/pl.json
index d03cefa..70efac1 100644
--- a/messages/pl.json
+++ b/messages/pl.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Darmowe narzędzie open-source do tworzenia profesjonalnych faktur PDF z podglądem w czasie rzeczywistym.<br></br><br></br>Nie jest oprogramowaniem księgowym. Brak gwarancji zgodności. Korzystając z tego narzędzia, akceptujesz <tosLink>Regulamin</tosLink>.",
"headings": {
+ "about": "O EasyInvoicePDF",
+ "solutions": "Rozwiązania",
"product": "Produkt",
"company": "Firma",
"community": "Społeczność"
diff --git a/messages/pt.json b/messages/pt.json
index 0d33e2c..a75ce8d 100644
--- a/messages/pt.json
+++ b/messages/pt.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Uma ferramenta gratuita de código aberto para criar faturas PDF profissionais com pré-visualização em tempo real.<br></br><br></br>Não é um software de contabilidade. Sem garantias de conformidade. Ao usar esta ferramenta, você concorda com os <tosLink>Termos de serviço</tosLink>.",
"headings": {
+ "about": "Sobre o EasyInvoicePDF",
+ "solutions": "Soluções",
"product": "Produto",
"company": "Empresa",
"community": "Comunidade"
diff --git a/messages/ru.json b/messages/ru.json
index f26949f..cd6c79a 100644
--- a/messages/ru.json
+++ b/messages/ru.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Бесплатный инструмент с открытым исходным кодом для создания профессиональных PDF-инвойсов с предпросмотром в реальном времени.<br></br><br></br>Не является бухгалтерским программным обеспечением. Никаких гарантий соответствия. Используя этот инструмент, вы соглашаетесь с <tosLink>Условиями использования</tosLink>.",
"headings": {
+ "about": "О EasyInvoicePDF",
+ "solutions": "Решения",
"product": "Продукт",
"company": "Компания",
"community": "Сообщество"
diff --git a/messages/uk.json b/messages/uk.json
index 2f69829..b5cfa53 100644
--- a/messages/uk.json
+++ b/messages/uk.json
@@ -57,6 +57,8 @@
"footer": {
"description": "Створюйте професійні рахунки за секунди за допомогою нашого безкоштовного інструменту з відкритим кодом. 100% у браузері, без реєстрації. Включає попередній перегляд PDF та шаблон у стилі Stripe - ідеально для фрілансерів, стартапів і малого бізнесу.<br></br><br></br>Не є бухгалтерським програмним забезпеченням. Жодних гарантій відповідності. Використовуючи цей інструмент, ви погоджуєтесь з <tosLink>Умовами використання</tosLink>.",
"headings": {
+ "about": "Про EasyInvoicePDF",
+ "solutions": "Рішення",
"product": "Продукт",
"company": "Компанія",
"community": "Спільнота"
diff --git a/src/app/(app)/components/invoice-page-header.tsx b/src/app/(app)/components/invoice-page-header.tsx
index 6612309..945530b 100644
--- a/src/app/(app)/components/invoice-page-header.tsx
+++ b/src/app/(app)/components/invoice-page-header.tsx
@@ -54,7 +54,18 @@ export function InvoicePageHeader({
<div className="relative bottom-2 mt-2 flex w-full flex-col justify-center sm:bottom-4 sm:mt-0">
<div className="flex items-center">
<ProjectLogo className="h-8 w-8" />
- <ProjectLogoDescription text="Free & Open-Source Invoice Generator" />
+ <ProjectLogoDescription
+ title={
+ <h1 className="text-balance text-xl font-bold text-slate-800 lg:text-2xl">
+ EasyInvoicePDF
+ </h1>
+ }
+ description={
+ <h2 className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
+ Free & Open-Source Invoice Generator
+ </h2>
+ }
+ />
</div>
</div>
{/* desktop only section (hidden on mobile) */}
diff --git a/src/app/(app)/loading.tsx b/src/app/(app)/loading.tsx
index 1e934fb..22dc7ab 100644
--- a/src/app/(app)/loading.tsx
+++ b/src/app/(app)/loading.tsx
@@ -1,15 +1,27 @@
-import { FooterSkeleton } from "@/app/(components)/footer-skeleton";
+import { Footer } from "@/app/(components)/footer";
+import { ProjectLogoDescription } from "@/app/(components)/project-logo-description";
+import { ProjectLogo } from "@/components/etc/project-logo";
export default function Loading() {
return (
<div className="flex flex-col items-center justify-start bg-gray-100 md:justify-center lg:min-h-screen">
{/* Main content */}
- <div className="mb-4 w-full max-w-[62rem] bg-white p-3 shadow-lg sm:my-4 sm:rounded-lg sm:p-4 min-[1400px]:max-w-7xl 2xl:max-w-[1480px]">
+ <div className="mb-4 w-full max-w-[62rem] bg-white p-3 shadow-lg sm:my-4 sm:rounded-lg sm:p-6 min-[1400px]:max-w-7xl 2xl:max-w-[1480px]">
+ <div className="relative bottom-2 mt-2 flex w-full flex-col justify-center sm:bottom-4 sm:mt-0">
+ <div className="flex items-center">
+ <ProjectLogo className="h-8 w-8" />
+ <ProjectLogoDescription
+ description={
+ <h2 className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
+ Free & Open-Source Invoice Generator
+ </h2>
+ }
+ />
+ </div>
+ </div>
<div className="grid grid-cols-1 gap-8 lg:grid-cols-12">
{/* Left side - Form */}
<div className="col-span-8 w-full space-y-6 lg:col-span-4">
- <div className="h-8 w-full animate-pulse rounded bg-gray-200 lg:w-64" />
-
{/* Form fields skeleton */}
<div className="space-y-4">
{Array.from({ length: 6 }).map((_, i) => (
@@ -35,7 +47,7 @@ export default function Loading() {
</div>
</div>
</div>
- <FooterSkeleton />
+ <Footer />
</div>
);
}
diff --git a/src/app/(app)/page.tsx b/src/app/(app)/page.tsx
index a279dab..723feba 100644
--- a/src/app/(app)/page.tsx
+++ b/src/app/(app)/page.tsx
@@ -31,7 +31,7 @@ const DEFAULT_TEMPLATE_META = {
const STRIPE_TEMPLATE_META = {
title: "Stripe Invoice Template - Create Free PDF Invoice",
- canonical: `${APP_URL}/`, // we use root URL as canonical for SEO purposes
+ canonical: `${APP_URL}/?template=stripe`, // self-referencing canonical so the Stripe template is indexed as its own page
images: [
{
url: `${STATIC_ASSETS_URL}/stripe-og.png?v=1755773921680`,
@@ -90,13 +90,10 @@ function buildTemplateMetadata(
* Resolves `robots` metadata for the main invoice app URL (`/`).
*
* Indexing is allowed only when `shouldIndex` is true (production deploy,
- * no shareable `?data=` payload). Otherwise behavior depends on template:
- * Stripe template URLs use `noindex` but `follow` so crawlers may discover links
- * without indexing a duplicate variant; all other non-indexable cases use strict
+ * no shareable `?data=` payload). All non-indexable cases use strict
* `noindex,nofollow` (including preview builds and share links).
*
- * @param shouldIndex - Whether this response should be treated as the canonical indexable homepage.
- * @param isStripeTemplate - Whether `template=stripe` is active (affects fallback when not indexable).
+ * @param shouldIndex - Whether this response should be indexable.
* @returns Next.js `Metadata.robots` object for this page.
*/
function resolveAppPageRobots(
diff --git a/src/app/(components)/footer-skeleton.tsx b/src/app/(components)/footer-skeleton.tsx
deleted file mode 100644
index cb70e7b..0000000
--- a/src/app/(components)/footer-skeleton.tsx
+++ /dev/null
@@ -1,62 +0,0 @@
-import { FooterLaunchBadges } from "@/app/(components)/footer-launch-badges";
-import { Skeleton } from "@/components/ui/skeleton";
-
-export function FooterSkeleton() {
- return (
- <footer className="w-full border-t border-slate-200 bg-white py-12 md:py-16">
- <div className="container mx-auto px-4 md:px-6">
- {/* Top content */}
- <div className="flex flex-col gap-10 md:flex-row">
- <div className="space-y-4 md:w-1/3">
- <div className="flex items-center gap-2">
- <Skeleton className="size-8" />
- <Skeleton className="h-7 w-40" />
- </div>
- <Skeleton className="h-16 w-full" />
- <div className="flex gap-4">
- <Skeleton className="size-5" />
- <Skeleton className="size-5" />
- </div>
- </div>
- <div className="grid grid-cols-1 gap-10 md:ml-20 md:flex-1 md:grid-cols-2">
- <div className="space-y-5">
- <Skeleton className="h-5 w-24" />
- <div className="space-y-2">
- {Array.from({ length: 5 }).map((_, i) => (
- <Skeleton key={i} className="h-4 w-40" />
- ))}
- </div>
- </div>
- <div className="space-y-5">
- <Skeleton className="h-5 w-24" />
- <div className="grid grid-cols-1 gap-6 sm:grid-cols-2">
- {Array.from({ length: 2 }).map((_, columnIndex) => (
- <div key={columnIndex} className="space-y-2">
- <Skeleton className="h-4 w-20" />
- {Array.from({ length: 4 }).map((_, i) => (
- <Skeleton key={i} className="h-4 w-32" />
- ))}
- </div>
- ))}
- </div>
- </div>
- </div>
- </div>
-
- {/* LAUNCH Badges */}
- <div className="mb-7 mt-10 flex flex-wrap items-center gap-3">
- <FooterLaunchBadges />
- </div>
-
- {/* Bottom links */}
- <div className="mt-10 flex flex-col items-center justify-between gap-4 border-t border-slate-200 pt-8 md:flex-row">
- <Skeleton className="h-4 w-48" />
- <div className="flex items-center gap-1.5">
- <Skeleton className="size-6 rounded-full" />
- <Skeleton className="h-4 w-40" />
- </div>
- </div>
- </div>
- </footer>
- );
-}
diff --git a/src/app/(components)/footer.tsx b/src/app/(components)/footer.tsx
index 759949f..7541f98 100644
--- a/src/app/(components)/footer.tsx
+++ b/src/app/(components)/footer.tsx
@@ -1,6 +1,7 @@
/* eslint-disable @next/next/no-html-link-for-pages */
import { FooterLaunchBadges } from "@/app/(components)/footer-launch-badges";
import { SEO_FOOTER_SOLUTION_LINKS } from "@/app/(seo-landings)/seo-landing-footer-links";
+import { LANGUAGE_TO_NATIVE_LABEL, SUPPORTED_LANGUAGES } from "@/app/schema";
import { ProjectLogo } from "@/components/etc/project-logo";
import {
DISCORD_COMMUNITY_URL,
@@ -14,6 +15,9 @@ import Link from "next/link";
interface FooterProps {
links?: React.ReactNode;
translations?: {
+ tagline: string;
+ aboutHeading: string;
+ solutionsHeading: string;
footerDescription: React.ReactNode;
footerCreatedBy: string;
resources: string;
@@ -25,6 +29,10 @@ export function Footer({ links, translations }: FooterProps) {
const footerDescription =
translations?.footerDescription ?? DEFAULT_FOOTER_DESCRIPTION;
+ const tagline =
+ translations?.tagline ?? "Free & Open-Source Invoice Generator";
+ const aboutHeading = translations?.aboutHeading ?? "About EasyInvoicePDF";
+ const solutionsHeading = translations?.solutionsHeading ?? "Solutions";
const footerCreatedBy = translations?.footerCreatedBy ?? "Made by";
const resources = translations?.resources ?? "Resources";
@@ -35,15 +43,20 @@ export function Footer({ links, translations }: FooterProps) {
<div className="space-y-4 md:w-1/3">
<div className="flex items-center">
<ProjectLogo className="size-8" />
- <p className="text-balance text-center text-xl font-bold text-slate-800 sm:mt-0 sm:text-2xl lg:mr-5 lg:text-left">
- <a
- href="https://easyinvoicepdf.com"
- target="_blank"
- rel="noopener noreferrer"
- >
- EasyInvoicePDF
- </a>
- </p>
+ <div className="flex flex-col -space-y-0.5">
+ <p className="text-balance text-xl font-bold text-slate-800 lg:text-2xl">
+ <a
+ href="https://easyinvoicepdf.com"
+ target="_blank"
+ rel="noopener noreferrer"
+ >
+ EasyInvoicePDF
+ </a>
+ </p>
+ <p className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
+ {tagline}
+ </p>
+ </div>
</div>
<p className="text-sm text-slate-700">{footerDescription}</p>
<div className="flex gap-4" data-testid="footer-logos-social-links">
@@ -86,25 +99,47 @@ export function Footer({ links, translations }: FooterProps) {
</div>
</div>
<div className="grid grid-cols-1 gap-10 md:ml-20 md:flex-1 md:grid-cols-2">
- <div className="space-y-5" data-testid="footer-solutions-links">
- <h3 className="text-base font-semibold text-slate-800">
- Solutions
- </h3>
- <ul className="space-y-2">
- {SEO_FOOTER_SOLUTION_LINKS.map(({ slug, label }) => (
- <li key={slug}>
- <Link
- href={`/${slug}`}
- className="text-sm text-slate-500 hover:text-slate-900"
- >
- {label}
- </Link>
- </li>
- ))}
- </ul>
+ <div className="order-2 space-y-10 md:order-1">
+ <div className="space-y-5" data-testid="footer-about-links">
+ <h3 className="text-lg font-semibold text-slate-800">
+ {aboutHeading}
+ </h3>
+ <ul className="grid grid-cols-2 gap-x-6 gap-y-2">
+ {SUPPORTED_LANGUAGES.map((lang) => (
+ <li key={lang}>
+ <Link
+ href={`/${lang}/about`}
+ className="text-sm text-slate-500 hover:text-slate-900"
+ >
+ {LANGUAGE_TO_NATIVE_LABEL[lang]}
+ </Link>
+ </li>
+ ))}
+ </ul>
+ </div>
+ <div className="space-y-5" data-testid="footer-solutions-links">
+ <h3 className="text-lg font-semibold text-slate-800">
+ {solutionsHeading}
+ </h3>
+ <ul className="space-y-2">
+ {SEO_FOOTER_SOLUTION_LINKS.map(({ slug, label }) => (
+ <li key={slug}>
+ <Link
+ href={`/${slug}`}
+ className="text-sm text-slate-500 hover:text-slate-900"
+ >
+ {label}
+ </Link>
+ </li>
+ ))}
+ </ul>
+ </div>
</div>
- <div className="space-y-5" data-testid="footer-social-links">
- <h3 className="text-base font-semibold text-slate-800">
+ <div
+ className="order-1 space-y-5 md:order-2"
+ data-testid="footer-social-links"
+ >
+ <h3 className="text-lg font-semibold text-slate-800">
{resources}
</h3>
{footerLinks}
@@ -112,7 +147,7 @@ export function Footer({ links, translations }: FooterProps) {
</div>
</div>
{/* LAUNCH Badges */}
- <div className="mb-7 mt-10 flex flex-wrap items-center gap-3">
+ <div className="mb-7 mt-10 flex flex-wrap items-center gap-3 md:mt-20">
<FooterLaunchBadges />
</div>
@@ -178,7 +213,7 @@ export function FooterLinkGroup({
}) {
return (
<div className="space-y-2">
- <p className="text-sm font-light uppercase tracking-wide text-slate-900">
+ <p className="text-sm font-semibold uppercase tracking-wide text-slate-700">
{heading}
</p>
<ul className="space-y-2">
diff --git a/src/app/(components)/header/header.client.tsx b/src/app/(components)/header/header.client.tsx
index db06f98..4f4d7c8 100644
--- a/src/app/(components)/header/header.client.tsx
+++ b/src/app/(components)/header/header.client.tsx
@@ -49,7 +49,11 @@ export function HeaderClient({
<div className="flex h-full items-center justify-between gap-4">
{/* App logo */}
<Logo
- text={translations.navLinks.tagline}
+ description={
+ <p className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
+ {translations.navLinks.tagline}
+ </p>
+ }
className="text-sm min-[375px]:text-base"
/>
diff --git a/src/app/(components)/header/language-switcher.tsx b/src/app/(components)/header/language-switcher.tsx
index fb7885b..8e790dc 100644
--- a/src/app/(components)/header/language-switcher.tsx
+++ b/src/app/(components)/header/language-switcher.tsx
@@ -1,5 +1,6 @@
"use client";
+import { LANGUAGE_TO_NATIVE_LABEL } from "@/app/schema";
import { usePathname, useRouter } from "@/i18n/navigation";
import { GlobeIcon } from "lucide-react";
import type { Locale } from "next-intl";
@@ -19,18 +20,10 @@ import {
} from "@/components/ui/tooltip";
import { cn } from "@/lib/utils";
-const MAP_LOCALE_TO_LANGUAGE = {
- en: "English",
- pl: "Polski",
- de: "Deutsch",
- es: "Español",
- pt: "Português",
- ru: "Русский",
- uk: "Українська",
- fr: "Français",
- it: "Italiano",
- nl: "Nederlands",
-} as const satisfies Record<Locale, string>;
+const MAP_LOCALE_TO_LANGUAGE = LANGUAGE_TO_NATIVE_LABEL satisfies Record<
+ Locale,
+ string
+>;
type SupportedLocale = keyof typeof MAP_LOCALE_TO_LANGUAGE;
type LanguageLabel = (typeof MAP_LOCALE_TO_LANGUAGE)[SupportedLocale];
diff --git a/src/app/(components)/header/logo.tsx b/src/app/(components)/header/logo.tsx
index 32b4c6f..6b71a00 100644
--- a/src/app/(components)/header/logo.tsx
+++ b/src/app/(components)/header/logo.tsx
@@ -3,10 +3,10 @@ import { ProjectLogoDescription } from "@/app/(components)/project-logo-descript
import { cn } from "@/lib/utils";
export function Logo({
- text,
+ description,
className,
}: {
- text: string;
+ description: React.ReactNode;
className?: string;
}) {
return (
@@ -16,7 +16,14 @@ export function Logo({
{/* show app logo and description on desktop */}
<div className="hidden sm:block">
- <ProjectLogoDescription text={text} />
+ <ProjectLogoDescription
+ title={
+ <p className="text-balance text-xl font-bold text-slate-800 lg:text-2xl">
+ EasyInvoicePDF
+ </p>
+ }
+ description={description}
+ />
</div>
{/* show only app name on mobile (to save space) */}
diff --git a/src/app/(components)/project-logo-description.tsx b/src/app/(components)/project-logo-description.tsx
index 1e0dcd6..08479c3 100644
--- a/src/app/(components)/project-logo-description.tsx
+++ b/src/app/(components)/project-logo-description.tsx
@@ -1,18 +1,28 @@
-export function ProjectLogoDescription({ text = "" }: { text: string }) {
+export function ProjectLogoDescription({
+ title,
+ description,
+}: {
+ title?: React.ReactNode;
+ description: React.ReactNode;
+}) {
return (
<div className="flex flex-col -space-y-0.5">
- <p className="text-balance text-xl font-bold text-slate-800 lg:text-2xl">
- <a
- href="https://easyinvoicepdf.com"
- target="_blank"
- rel="noopener noreferrer"
- >
- EasyInvoicePDF
- </a>
- </p>
- <h1 className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
- {text}
- </h1>
+ <a
+ href="https://easyinvoicepdf.com"
+ target="_blank"
+ rel="noopener noreferrer"
+ >
+ {title || (
+ <h1 className="text-balance text-xl font-bold text-slate-800 lg:text-2xl">
+ EasyInvoicePDF
+ </h1>
+ )}
+ </a>
+ {description || (
+ <h2 className="text-balance text-[12px] text-slate-700 sm:text-[13px]">
+ Free & Open-Source Invoice Generator
+ </h2>
+ )}
</div>
);
}
diff --git a/src/app/[locale]/about/loading.tsx b/src/app/[locale]/about/loading.tsx
index 65364cd..9d758b5 100644
--- a/src/app/[locale]/about/loading.tsx
+++ b/src/app/[locale]/about/loading.tsx
@@ -1,4 +1,4 @@
-import { FooterSkeleton } from "@/app/(components)/footer-skeleton";
+import { Footer } from "@/app/(components)/footer";
import { HeaderSkeleton } from "@/app/(components)/header/header-skeleton";
import { Skeleton } from "@/components/ui/skeleton";
@@ -57,11 +57,11 @@ export default function AboutLoading() {
</div>
</section>
- {/* Newsletter Section */}
+ {/* FAQ Section */}
<section className="flex w-full items-center justify-center bg-white py-12 md:py-24">
<div className="container px-4 md:px-6">
<div className="flex flex-col items-center justify-center space-y-4 text-center">
- <div className="space-y-2">
+ <div className="w-full space-y-2">
<Skeleton className="mx-auto h-10 w-[60%]" />
<Skeleton className="mx-auto h-16 w-[80%]" />
</div>
@@ -75,24 +75,20 @@ export default function AboutLoading() {
{/* CTA Section */}
<section className="flex w-full items-center justify-center bg-slate-900 py-12 md:py-24 lg:py-32">
<div className="container px-4 md:px-6">
- <div className="flex flex-col items-center justify-center space-y-4 text-center">
- <div className="space-y-2">
- <Skeleton className="mx-auto h-10 w-[60%]" />
- <Skeleton className="mx-auto h-16 w-[80%]" />
- </div>
+ <div className="flex flex-col items-center justify-center space-y-4">
+ <Skeleton className="h-4 w-[200px]" />
<div className="flex w-full flex-col items-center justify-center gap-6">
- <div className="flex w-full flex-col justify-center gap-2 md:flex-row">
+ <div className="flex gap-2">
<Skeleton className="h-11 w-[160px]" />
<Skeleton className="h-11 w-[160px]" />
</div>
</div>
- <Skeleton className="h-4 w-[200px]" />
</div>
</div>
</section>
</main>
- <FooterSkeleton />
+ <Footer />
</div>
);
}
diff --git a/src/app/[locale]/about/page.tsx b/src/app/[locale]/about/page.tsx
index bdaed50..fa0ea16 100644
--- a/src/app/[locale]/about/page.tsx
+++ b/src/app/[locale]/about/page.tsx
@@ -84,6 +84,9 @@ export default function AboutPage({ params }: { params: { locale: Locale } }) {
</main>
<Footer
translations={{
+ tagline: t("tagline"),
+ aboutHeading: t("footer.headings.about"),
+ solutionsHeading: t("footer.headings.solutions"),
footerDescription: t.rich("footer.description", {
br: () => <br />,
tosLink: (chunks) => (
@@ -209,7 +212,7 @@ function HeroSection() {
</h1>
<div className="flex justify-center xl:justify-start">
- <p className="text-pretty px-4 text-center text-base text-slate-600 md:max-w-[500px] md:text-lg lg:px-0 xl:text-left xl:text-lg">
+ <h2 className="text-pretty px-4 text-center text-base text-slate-600 md:max-w-[500px] md:text-lg lg:px-0 xl:text-left xl:text-lg">
{(() => {
let colorIndex = 0;
@@ -235,7 +238,7 @@ function HeroSection() {
},
});
})()}
- </p>
+ </h2>
</div>
</div>
diff --git a/src/app/schema/i18n-schema.ts b/src/app/schema/i18n-schema.ts
index 52d1807..8e448ea 100644
--- a/src/app/schema/i18n-schema.ts
+++ b/src/app/schema/i18n-schema.ts
@@ -62,6 +62,8 @@ const aboutSchema = z
description: z.string(),
headings: z
.object({
+ about: z.string(),
+ solutions: z.string(),
product: z.string(),
company: z.string(),
community: z.string(),
diff --git a/src/app/schema/index.ts b/src/app/schema/index.ts
index 3103fb6..906faf2 100644
--- a/src/app/schema/index.ts
+++ b/src/app/schema/index.ts
@@ -685,6 +685,24 @@ export const LANGUAGE_TO_LABEL = {
nl: "Dutch",
} as const satisfies Record<SupportedLanguages, string>;
+/**
+ * Mapping from language code to its native language label.
+ * Used for language selectors, footer, and UI where displaying the language in its native form is preferred.
+ * Example: { en: "English", pl: "Polski" }
+ */
+export const LANGUAGE_TO_NATIVE_LABEL = {
+ en: "English",
+ pl: "Polski",
+ de: "Deutsch",
+ es: "Español",
+ pt: "Português",
+ ru: "Русский",
+ uk: "Українська",
+ fr: "Français",
+ it: "Italiano",
+ nl: "Nederlands",
+} as const satisfies Record<SupportedLanguages, string>;
+
export const SUPPORTED_DATE_FORMATS = [
"YYYY-MM-DD", // 2024-03-20 (default template date format)
"DD/MM/YYYY", // 20/03/2024
diff --git a/src/app/sitemap.ts b/src/app/sitemap.ts
index b6047e2..77fde70 100644
--- a/src/app/sitemap.ts
+++ b/src/app/sitemap.ts
@@ -17,6 +17,13 @@ export default async function sitemap(): Promise<MetadataRoute.Sitemap> {
changeFrequency: "daily",
priority: 1,
},
+ // Stripe invoice template variant of the main app page
+ {
+ url: `${APP_URL}/?template=stripe`,
+ lastModified,
+ changeFrequency: "daily",
+ priority: 1,
+ },
// About pages in all languages
...SUPPORTED_LANGUAGES.map((locale) => ({
url: `${APP_URL}/${locale}/about`,
diff --git a/src/lib/seo/indexing-utils.ts b/src/lib/seo/indexing-utils.ts
index bc84a8b..160e599 100644
--- a/src/lib/seo/indexing-utils.ts
+++ b/src/lib/seo/indexing-utils.ts
@@ -17,6 +17,7 @@ export function computeIndexingFlags(searchParams: {
const isProd =
process.env.VERCEL_ENV === "production" &&
`https://${process.env.VERCEL_PROJECT_PRODUCTION_URL}` === PROD_WEBSITE_URL;
+
const shouldIndex = isProd && !hasShareableData;
return { hasShareableData, isProd, shouldIndex };
diff --git a/src/lib/seo/site-entities.ts b/src/lib/seo/site-entities.ts
index b346052..4ef1fc7 100644
--- a/src/lib/seo/site-entities.ts
+++ b/src/lib/seo/site-entities.ts
@@ -33,7 +33,7 @@ export const FOUNDER_PAGE_URL = `${PROD_WEBSITE_URL}/founder`;
export const FOUNDER_PAGE_TITLE = "Vlad Sazonau | Founder of EasyInvoicePDF";
export const FOUNDER_PAGE_DESCRIPTION =
- "Meet Vlad Sazonau, founder of EasyInvoicePDF, the free open-source invoice PDF generator with live preview. Product engineer and design enthusiast with 8+ years building digital products.";
+ "Meet Vlad Sazonau, founder of EasyInvoicePDF, the free open-source invoice PDF generator with live preview. Product engineer and design enthusiast.";
export const OG_IMAGE_URL = `${STATIC_ASSETS_URL}/easy-invoice-opengraph-image.png?v=1755773879597`;