Add a years_json column listing every event the speaker has appeared at, and a list mapping renders an appearance history block. Alternatively, run one page group per event with separate sheets so each year has its own URL space, and link between them with selector-injected related-talk cards.

Either delete the row or set a status column to cancelled, then flush the cache. The URL stops resolving on the next request. If the page had backlinks, set up a 301 in your redirect plugin to the track page or main speakers index to preserve link equity.

Yes. SleekRank exposes every generated URL through its sitemap and noindexes the base template page automatically. Submit the sitemap in Search Console once; new roster rows start getting crawled after the next rewrite flush, and removed rows drop from the sitemap on the same cycle.

Yes. Add the JSON-LD block to the base template once and inject row-specific values like name, jobTitle, image, and sameAs through selector or meta mappings. For the talk block, render Event JSON-LD with startDate, location, and performer pulled from the same row, all from one mapping configuration.

No. The base WordPress page provides one layout that every row shares, which keeps the speaker hub visually consistent. For variation by track or speaker type, carry a layout_variant column and use selector mapping to add or remove blocks per row, like swapping in a workshop sign-up vs a keynote video embed.

Not by default. Every row has a unique bio, talk title, and abstract. Where rows risk thin uniqueness, like a brief keynote line, carry a long-form bio_long column and a per-talk abstract that runs at least 80 words. Carry a noindex flag column for any row that should not be indexed individually.

Cache duration is configurable per page group, typically 3,600 to 86,400 seconds depending on how close to the event you are. The week before the event, drop cacheDuration to 600 seconds or run wp db query "DELETE FROM wp_319_sleek_rank_items" after any major lineup change to force an immediate refresh.

Yes. Run two page groups against the same urlPattern with a filter column distinguishing CMS-managed speakers from sheet-managed ones. Or use a thin REST proxy that merges sources upstream and returns one feed. SleekRank caches the proxy response, so the merge only runs at refresh time.