Yes. Add a JobPosting JSON-LD block to the base page template and use selector mappings to inject the row data into the script tag, or render schema directly from columns. Required Google for Jobs fields like title, datePosted, validThrough, hiringOrganization, employmentType, and jobLocation all map cleanly to columns. Each posting inherits the schema without per-role configuration.

Run a second page group with a small cities source listing the cities you want to cover, then use a list mapping to render the matching jobs from the main jobs feed onto each city page. The city page stays current automatically because both groups read the same job feed; new roles in Berlin appear on the Berlin page on the next cache cycle.

Remove the row from the feed. On the next cache cycle the page returns a 404 and drops out of the sitemap. Add a redirect to a closed-roles archive at the server level if needed for link equity. Most boards just let closed roles 404 because Google handles the de-indexing fast and the role is genuinely gone, not relocated.

If the ATS exposes a JSON or REST feed of open roles, and most do, point SleekRank at it. Workable, Lever, Greenhouse, Ashby, Personio, and similar platforms all expose feeds for this kind of integration. The feed URL is usually documented under the careers integration or jobs API section. SleekRank caches the feed for the duration you set and serves cached rows on every page render.

Each row produces a real URL with its own metadata and sitemap entry, plus JobPosting JSON-LD if you wired the template that way. Indexing depends on content quality, schema validity, and site authority. SleekRank does not submit URLs to indexing-as-a-service providers; it produces the pages and the sitemap, and Google handles discovery from there.

Not directly. Manage paid postings in your sheet or database with a paid flag column, and use the flag in the template to show featured styling, a highlight border, or a top-of-page placement on the city collection page. Payments and gating need a separate plugin. SleekRank handles the page generation and styling logic; the transaction is elsewhere.

Add an applyUrl column to the feed and inject it into the apply button via selector mapping. The button can deep-link to the ATS application form or open an embedded form. SleekRank does not handle form submissions itself; pair it with the ATS-hosted form, Gravity Forms, or Fluent Forms depending on whether you want the application to land in the ATS or your CRM.

As fresh as your cache duration allows. A one-hour cache means roles published in the ATS go live within an hour and closed roles drop within an hour. Shorter caches put more load on the ATS endpoint; longer caches reduce load but increase staleness. Most boards run a one to four hour cache for an acceptable balance between freshness and ATS load.