SleekRank reads whatever you put in the expansions sheet. Source from style guides, dictionaries, or your own editorial team. The plugin renders pages from the data; the underlying lexicography is yours to curate. Quality of expansions and usage examples drives whether the pages earn their place in the index.

Carry one expansion row per meaning, each tagged with its usage_context. List mapping groups them on the page. /abbreviation/st/ shows Street under Address context and Saint under Religious context, each in its own section, with example sentences showing when to use which.

Acronyms (API, CRM, SaaS) are read as one word or letter-by-letter and usually expand to a full phrase. Abbreviations (St., e.g., TBA) are short forms of words or phrases. The data model is similar; many sites run separate page groups for the two with different URL patterns to match search intent.

Append a row to the abbreviations sheet with slug, abbreviation, category, and intro. Add its expansion rows to the expansions sheet with usage_context, definition, and example. After cacheDuration elapses or you clear the items table, /abbreviation/{slug}/ resolves and lands in the sitemap on the next rewrite flush.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new abbreviation rows start getting crawled after the next rewrite flush.

Yes. Use meta mapping at og:image pointing to a per-abbreviation image URL column, or pair with SleekPixel and a templated suffix so /abbreviation/fyi/ and /abbreviation/tba/ each render their own preview with abbreviation and primary expansion without manual asset work.

Yes. Add the JSON-LD block to the base template once and inject row-specific values like name, alternateName, and description through selector or meta mappings. Each /abbreviation/{slug}/ renders its own valid schema sourced from the matching row.

Style conventions shift over time (e.g. "e.g." sometimes loses its periods). Edit the affected rows or add new ones flagged with their convention, clear the items table, and flush rewrites. The page reflects current guidance. Keep a style_source column if you want to track which style guide informs each row.