Page Header & Icons/Structured Data Generator
Generate a complete, SEO-friendly
section with favicons (.ico + PNG), Apple touch icons, Android PWA manifest and icons, Windows tiles, Open Graph/Twitter images, and JSON-LD—plus a ZIP of all resized images. 100% private, browser-only.- Enter Site Name, Canonical URL, Title, and Description.
- Upload the Icon (square, required) and optional Logo (landscape PNG/JPG/GIF) for social previews.
- Set Icons Base Path and Logos Base Path (defaults below).
- Pick your outputs, then Generate & download assets.
Frequently Asked Questions
What does this tool produce?
A complete <head>
snippet plus favicons, Apple/Android/Windows icons, Open Graph/Twitter images, JSON‑LD, and a ZIP of all assets—generated locally in your browser.
What do I need to enter (and how do the counters work)?
Provide Site Name, Canonical URL, Title, and Description. Title sweet spot is 50–60 characters; description 140–160 characters; canonical URL must start with http://
or https://
.
Counters: the built‑in length counters show red when you’re under the recommended length and turn green once you’re in range.
What image types can I upload?
- Icons: PNG, JPG, SVG (a real ICO file is generated for you).
- Social logos: PNG, JPG; animated GIF is accepted (may not animate everywhere).
Will images be upscaled?
No—larger‑than‑source sizes are disabled. For best coverage, supply an icon at least 512×512 and a social logo at least 1200×630.
What sizes/formats are generated?
- Favicons: 16, 32, 48, 64, 96, 128, 192 px
- Apple Touch: 120, 152, 167, 180 px
- Android (maskable): 192, 512 px
- Windows tiles: 144, 150, 310×150, 310 px
- Open Graph: 1200×630 px
- Twitter: 1200×628 px
Note: The exact set can vary by options selected.
Where should I put the files (and what’s in the ZIP)?
Defaults: /assets/icons
(icons) and /assets/logos
(social). Always copy /favicon.ico
to the site root.
The ZIP includes all generated images, the real favicon.ico
, and manifest.json
when Android is selected. Filenames follow conventional patterns.
How do platforms treat these assets?
- iOS: uses
apple-touch-icon
links. - Android: uses the Web App Manifest (icons, theme colors, maskable).
- Windows: supports PWAs and
msapplication-*
tiles/meta.
What structured data is included?
JSON‑LD for WebSite, Organization (with optional sameAs
), and WebPage; context is https://schema.org
. A “Force http://” option exists, but HTTPS is recommended.
Any performance & validation tips?
- Use long cache lifetimes and versioned filenames for static assets.
- Ensure asset paths aren’t blocked by redirects or auth.
- Validate OG/Twitter previews, iOS/Android install behavior, Windows tiles, and JSON‑LD with platform validators.
Is anything uploaded?
No. Everything runs locally in your browser.