When someone googles "remote react jobs", the winning result is rarely a generic job-board home page; it's a dedicated page about exactly that search. Search pages let you build those: each one binds a live job filter to its own indexable URL (like /s/remote-react-jobs) with its own title, meta description and intro copy. Because the filter runs live, the page always lists your current matching jobs and never goes stale.
Published search pages are also linked from your board's footer and included in your sitemap, so search engines discover them on their own.
Create a search page
At the bottom of the sidebar, click Settings, open the SEO card, and make sure you are on the Search pages tab (it's the first one).
Click Add search page.
Fill in the Details card and the Job filters card (both explained below).
Click Create page.
You should see a "Search page created" confirmation and land on the page's edit screen. Back on the list, the new page appears with a Published badge and a view action that opens it live at /s/your-slug.
The Details card
Title: shown as the page's on-page heading (H1). Make it read like the search itself: "Remote React Jobs", not "Page 1".
Slug: the URL after
/s/. It auto-fills from the title (lowercase, hyphens) until you edit it; only lowercase letters, numbers and hyphens are allowed.Meta title: the
<title>tag, used verbatim when set. Leave blank to get "Title | board name" automatically, which is usually fine.Meta description: a one- or two-sentence summary for search results.
Intro content: optional rich-text copy shown under the heading. This is the part most boards skip and shouldn't: a paragraph or two about the niche (what kinds of roles, typical salary range, why work in this field) is exactly the crawlable context that makes the page rank. Images and video are not available here, by design.
Published: on by default. When off, the page is a draft: it returns a 404 to visitors and stays out of the sitemap and footer until you flip it back on.
The Job filters card
These decide which published jobs the page lists. Leave any filter empty to not filter by it; the filters you do set are combined.
Search term: matches against the job title and company name. "react" catches "Senior React Developer" and "React Native Engineer".
Job type: limit to one of your job types (Full-time, Contract, and so on), or leave on Any job type.
Category: limit to one of your job categories, or leave on Any category. Manage both under Job types and categories.
Location: matches anywhere in the job's location text; "Berlin" catches "Berlin, Germany" and "Remote (Berlin preferred)".
Remote jobs only: switch on to only show jobs marked as remote.
Edit, unpublish, or check a page later
Go back to Settings, then SEO, then the Search pages tab.
The table lists every page with its title, path and a Published or draft status badge.
Use the row's view action to open the live page, or the edit action to change details and filters. Edits save with Save changes and apply immediately.
Why a search page beats a filtered URL
You might wonder why not just share a filtered jobs URL like /jobs?q=react&remote=true. Two reasons. First, your board deliberately keeps query-string filter combinations out of search engines (they create endless near-duplicate URLs that dilute ranking); a search page's clean path like /s/remote-react-jobs is the version search engines are invited to index. Second, a search page carries its own title, meta description and intro copy, which a raw filter URL never can. Same jobs, but only one of the two can rank.
Which pages to create
Make one page per distinct search your audience really types, typically combinations of role, technology, location and remote:
"Remote React jobs" (search term react, remote only)
"Marketing jobs in Berlin" (category Marketing, location Berlin)
"Part-time design jobs" (job type Part-time, category Design)
Start with two or three where you genuinely have jobs to show. A landing page listing zero jobs doesn't convert and doesn't rank; you can always add more pages as your board grows.
Tip: search pages complement, not replace, the metadata of your main pages. For the home page, blog index and pricing page, use Custom SEO content. And once Search performance has data, mine its top-queries table for search-page ideas you haven't covered yet.