Summary
APN's distinct public pages at /privacy, /bug, and /help all publish the same generic browser title and social-sharing metadata as the homepage.
Each page currently contains:
<title>APN</title>
<meta content="APN" property="og:title">
<meta content="Censorship-resistant VPN, hardest to block by design, with fast nodes in many countries" property="og:description">
<meta content="APN" name="twitter:title">
<meta content="Censorship-resistant VPN, hardest to block by design, with fast nodes in many countries" name="twitter:description">
The canonical/Open Graph URL changes correctly per route, but the title and description do not identify the actual page.
Steps to reproduce
- Open https://apn.tech/privacy
- View the page source or inspect the document head.
- Observe that the browser title, Open Graph title, and Twitter title are all only
APN.
- Observe that both social descriptions use the homepage's generic VPN marketing text rather than describing the privacy policy.
- Repeat for:
- Compare with the visible page headings and purposes: Privacy Policy, bug reporting, and interactive help.
Actual result
Different functional pages expose identical homepage metadata. Browser tabs are indistinguishable by title, and links shared in services that read Open Graph or Twitter Card metadata display a generic APN/VPN preview instead of identifying the privacy policy, bug form, or help assistant.
This also affects every supported language: the HTML lang and page content change, while the title/social description remain the same English homepage metadata.
Expected result
Each route should provide page-specific and localized metadata, for example:
APN Privacy Policy with a privacy-policy descriptionReport an APN Bug with a bug-report descriptionAPN Help with a support-assistant description
The Open Graph and Twitter fields should match the route and selected language.
Impact
Users cannot distinguish these pages in browser tabs or link previews. A shared privacy-policy or bug-report link looks like a generic product homepage, which makes the destination unclear and reduces trust in support and privacy links.
Duplicate check
I searched the tracker for Open Graph, og:title, social preview, browser title, meta description, and Twitter card. I found no existing report about route-specific pages reusing the homepage metadata.
This is separate from #162, which concerns incorrect iOS wording in the external App Store product description.
Environment
Observed on July 15, 2026 on the public APN website (site build 341a88c) in English, Russian, Chinese, Arabic, and Turkish. The check used only public GET requests and page-source inspection; no login, form submission, account access, or destructive testing was performed.
Summary
APN's distinct public pages at
/privacy,/bug, and/helpall publish the same generic browser title and social-sharing metadata as the homepage.Each page currently contains:
The canonical/Open Graph URL changes correctly per route, but the title and description do not identify the actual page.
Steps to reproduce
APN.Actual result
Different functional pages expose identical homepage metadata. Browser tabs are indistinguishable by title, and links shared in services that read Open Graph or Twitter Card metadata display a generic APN/VPN preview instead of identifying the privacy policy, bug form, or help assistant.
This also affects every supported language: the HTML
langand page content change, while the title/social description remain the same English homepage metadata.Expected result
Each route should provide page-specific and localized metadata, for example:
APN Privacy Policywith a privacy-policy descriptionReport an APN Bugwith a bug-report descriptionAPN Helpwith a support-assistant descriptionThe Open Graph and Twitter fields should match the route and selected language.
Impact
Users cannot distinguish these pages in browser tabs or link previews. A shared privacy-policy or bug-report link looks like a generic product homepage, which makes the destination unclear and reduces trust in support and privacy links.
Duplicate check
I searched the tracker for
Open Graph,og:title,social preview,browser title,meta description, andTwitter card. I found no existing report about route-specific pages reusing the homepage metadata.This is separate from #162, which concerns incorrect iOS wording in the external App Store product description.
Environment
Observed on July 15, 2026 on the public APN website (site build
341a88c) in English, Russian, Chinese, Arabic, and Turkish. The check used only public GET requests and page-source inspection; no login, form submission, account access, or destructive testing was performed.