Cache duration is configurable per page group. Setting it to 60 seconds means scores refresh at most once a minute, which is plenty for nearly any public scoreboard without rate-limiting the source. Shorter intervals are possible, but most stats APIs throttle or bill per call, so 60 to 120 seconds is a healthy floor for live games.

Yes. A single sheet or REST source can carry every fixture for a season, with the slug column generating one URL per row. SleekRank's cache layer keeps the rendering cheap even when the source carries thousands of rows, because each row is fetched and rendered only when its URL is requested or its cache expires.

Yes. SleekRank injects values into the base WordPress page through selector mappings, so whatever scoreboard table, card or live-region markup the theme already uses keeps working. Bricks, Elementor, Gutenberg blocks and Twig templates all render the same content through the same mappings.

Yes. SleekRank includes every resolved fixture URL in the XML sitemap and noindexes the base template page automatically. New fixtures show up after the next rewrite flush, so adding a game means appending a row and running wp rewrite flush once, not editing sitemap config per fixture.

Yes. Add a sport column with values like soccer, basketball or baseball, and use a selector mapping to toggle a class on the scoreboard container. The base page reads the class and applies sport-specific CSS. For radically different layouts, run multiple page groups against the same source filtered by sport.

Set the row's status column to cancelled and adjust the template to render a cancellation banner via selector mapping. If you prefer the URL to 404 instead, delete the row, which clears the cache, drops the sitemap entry and returns 404 cleanly. Either pattern is supported.

Each fixture page carries a unique title, meta description, team names and score, so the rendered text differs row to row even when the chrome is identical. Add a recap_text column for a per-fixture paragraph if you want richer differentiation, and search engines treat each URL as a distinct page.

Yes. Add a SportsEvent script block to the base page and populate it via selector or meta mappings tied to the same fixture row. The structured data picks up the same home, away, score and date values the visible table renders, so the schema stays in sync with the page without a separate maintenance loop.