SEO and Sharing

Set clear metadata for search, social previews, product pages, and launch confidence.

SEO in Taintless is meant to make the storefront understandable. Write for the customer first, then for search.

Good metadata answers three questions:

What is this page?
Who is it for?
Why should someone click it?

Feature Availability

SEO surface	Plan
Site-wide SEO title and description	Pro and Ultra
Site-wide social image	Pro and Ultra
Page SEO overrides	Ultra
Product SEO overrides	Ultra
JSON-LD structured data	Ultra

Product SEO is product specific

Product SEO is saved on a real product. The default product preview is for design defaults and does not publish product SEO metadata.

Media placeholder

SEO editor review

Recommended asset: screenshot of a finished SEO editor with title, description, social image, and health score visible.

Site-Wide SEO

Set site-wide SEO first. These values create the baseline for the storefront.

Field	Good direction
Title	Store name plus the core offer
Description	One clear sentence about the catalog and audience
Social image	A clean brand image or storefront preview
Favicon	Small, recognizable brand mark

Example:

Northline Scripts | Premium FiveM Resources

Browse verified FiveM scripts for roleplay servers, review product details, and check out securely through Tebex.

Avoid claims that customers cannot verify. "Best scripts on the market" is weaker than naming the product type, audience, and purchase path.

Page SEO

Use page SEO when a page has its own search intent.

Page	Good title direction	Good description direction
Home	Store name and broad offer	What the store sells and who it serves
Products	Product catalog or main category	What customers can browse and buy
Subscriptions	Membership or subscription offer	What is included and why it renews
Support	Store support	How customers get help

Do not write every page with the same title. Search previews become more useful when each page has a clear job.

Product SEO

Use product SEO on important products.

Prioritize:

Best sellers
High margin products
Products used in ads
Products with complex requirements
Products that need a better summary than the raw Tebex description

Product descriptions should explain what the customer gets. Keep compatibility notes, requirements, and delivery expectations visible before checkout.

Social previews are often where customers first see the store. A good preview image should be readable at small size and should not depend on tiny text.

Use:

Store logo
Strong product image
Clean background
Short headline if text is needed
High contrast

Avoid:

Busy screenshots
Tiny product grids
Unreadable discount text
Placeholder art
Cropped logos

Indexing Rules

Published stores are designed to be indexed. Draft, unpublished, suspended, and demo-style storefronts should not be treated as public search targets.

After launch, check:

The store is published.
The public domain opens without preview parameters.
The title is correct in the browser tab.
Social previews use the right image.
Product detail pages have meaningful titles.

Writing Better Metadata

Use this format when a page feels hard to write:

[Specific offer] for [specific audience] | [store name]

Examples:

FiveM Police Scripts for Roleplay Servers | Northline Scripts

Monthly FiveM Script Access | Northline Scripts

For descriptions, use one sentence:

Browse tested FiveM police scripts with clear requirements, update notes, and secure Tebex checkout.

Final SEO Checklist

Site title is not generic
Site description says what the store sells
Social image is not a placeholder
Products page has a clear catalog description
Important products have product-specific metadata
Support page explains how customers get help
Published URL works without preview parameters
Custom domain, if used, opens the same store
Product descriptions are readable when shared

SEO should feel quiet. A customer should know where they are before they click, and search tools should have enough clean information to describe the page correctly.