A page without a description gets a random snippet in search. MetaShift generates SEO and Open Graph meta tags with a live HTML snippet you can paste into a head. Use it to draft title, description, canonical, og:image notes, and twitter card bits for a static page. Do not use it as a rank guarantee, a crawler, or a full schema.org studio. Length still matters: titles get cut, descriptions get cut. WordShift can count. The snippet is HTML; HtmlShift can encode a stray ampersand. Preview in a debugger; do not trust a form field as Google.
Fill title, description, canonical URL, maybe OG title if it should differ. Copy the tag block. Put it in the real document head, not in a blog body. og:image needs an absolute URL to a real image you actually deployed. A generator cannot host the PNG. Duplicate OG and twitter tags are common and usually harmless if they match.
When not to use it: a JS-only SPA that never server-renders the tags (crawlers may still see empty). That is a site architecture problem this form will not fix. Also skip keyword stuffing. A keywords meta tag is mostly nostalgia. Write a description a human would click. Keyword stuffing is nostalgia; write a description a human would click, then stop.
Privacy is local. Unreleased page titles stay in the tab until you commit them. QRShift can encode the canonical URL for a print flyer. SlugShift helps the path. None of this replaces Search Console. Canonical to the URL you want indexed; mixing subdomain and path is how you compete with yourself.
Title: 'ImageShift — HEIC to WebP in the browser.' Description: 150 characters about on-device convert. Canonical: https://altarmm.com/imageshift/. MetaShift emits the tag block. You paste it into the static HTML. og:image points at a 1200x630 PNG you actually uploaded. The share debugger shows the card. A keywords tag stuffed with 'free free free' is not generated because you did not ask it to be a clown. Work stayed local until git.
MetaShift builds snippets in the browser. Titles and descriptions stay on the device until you commit them. There is no SEO account. Close the tab when the tags are in the repo. Titles and descriptions stay on the device until you commit them; there is no SEO account watching the form.
Full policy: Shift Privacy Policy. Questions: [email protected].
Aim to be useful before a typical cutoff, often around 150 to 160 characters. Write for humans who see the snippet, then stop. Stuffing extra keywords past the fold does not help a click and can make the card look spammy.
Sometimes, when the share card should be punchier than the browser tab. Keep them honest. Clickbait in OG and a dry title in the tab feels like a bait-and-switch. A punchier OG title is fine; clickbait in the card and a dry tab title still feels like a bait-and-switch.
No. Indexing needs a crawlable page with real content. Tags help snippets. They do not invent a site. Indexing needs a crawlable page with real content; tags help snippets and do not invent a website.
Pick the URL you want indexed and stick to it. Mixed subdomain and path duplicates are how you compete with yourself. Pick the canonical host and path and stick to it so you are not ranking against your own alias.
Related tools: HtmlShift · SlugShift · QRShift
Guides · All Shift tools · About · Contact