SleekRank reads whatever you put in the sheet. Source the list from your own editorial team, license a dataset, or import from a public-domain corpus. The plugin renders pages from the data; the underlying lexicography is yours to curate. Quality of definitions and synonym choices drives whether the pages earn their place in the index.

Two patterns work. Either keep one row per word with grouped synonyms by sense in a structured field, or split senses into separate rows like /word/run-verb/ and /word/run-noun/ with distinct slugs. The second approach gives each sense its own URL but doubles the row count; pick based on how much sense-specific content you carry.

Yes, that is the core pattern. Carry synonyms as pipe-separated slugs, and the list mapping renders each as an anchor tag pointing to /word/{slug}/. Existing pages automatically become destinations when you add new words that name them as synonyms, after the next cache flush.

Append a row to the words sheet with slug, headword, part-of-speech, definition, synonyms, antonyms, example, and audio_url. After cacheDuration elapses or you clear the items table, /word/{slug}/ resolves and lands in the sitemap on the next rewrite flush. Existing pages that reference the new word as a synonym start linking to it automatically.

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

Yes. Use meta mapping at og:image pointing to a per-word image URL column, or pair with SleekPixel and a templated suffix so /word/happy/ and /word/difficult/ each render their own preview with headword and synonym count without manual asset work.

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

The chip still renders, but the link points to a missing URL. Either keep a status column the list mapping respects so unbuilt synonyms render as plain text instead of links, or backfill the missing word rows so every chip resolves. Both patterns are common during initial dataset growth.