Straight into Elementor
Each found page opens at action=elementor — the Elementor canvas — instead of the front end, so you land ready to edit.
Paste your normal page URLs and open every one in the Elementor editor or the WordPress editor at once. Post IDs are looked up automatically from the WP REST API — no IDs to hunt for, no plugin to install.
Opening several editor tabs at once is exactly what pop-up blockers stop.
IDs come from the site's WordPress REST API (public, no login). Editor links point at /wp-admin/, so you must be logged into that WordPress site in the same browser for editors to load.
Nothing saved yet. Save a list to reuse it later — it stays in this browser only, never on our servers.
Step 1 — Resolve the ID. The tool takes the slug from each URL and calls yoursite.com/wp-json/wp/v2/pages?slug=your-slug (and /posts), straight from your browser. This returns the numeric post or page ID with no login.
Step 2 — Subdirectory installs. If the site root has no match, it also tries the first path segment — so a site under example.com/blog/ resolves against example.com/blog/wp-json/, and its editor links point at /blog/wp-admin/.
Step 3 — Proxy fallback. If your browser blocks the direct call, the tool retries via the public corsproxy.io service, which then sees the URL being looked up — never any credentials.
Step 4 — Open the editor. For each found page it opens /wp-admin/post.php?post=ID&action=elementor (Elementor) or &action=edit (WP editor). You must be logged into that site or WordPress shows its login screen instead.
“Only one tab opened”. That is the pop-up blocker. Allow pop-ups for this page (the tool shows how), then click Open editors to open the rest.
“Not found”. The REST API answered but had no match — a draft, a differing slug, or a custom post type not exposed to the API. “Blocked”. Both the direct request and the proxy failed — the REST API is disabled or behind bot protection.
| URL | ID | Type | Status | Open in |
|---|
Ctrl+Enter fetch & open · Alt+R clear everything
Stop opening pages one at a time. Paste a list of URLs and this tool resolves every post ID and launches the right editor for each — built for agencies and site owners doing rounds of edits across many pages.
Each found page opens at action=elementor — the Elementor canvas — instead of the front end, so you land ready to edit.
Prefer Gutenberg or the classic editor? Switch to WP Editor and every page opens at action=edit instead. Or pick Both.
No post IDs to dig for. The tool reads each slug and queries the WordPress REST API to get the numeric ID automatically.
A tab-delay slider paces the opens, and if the browser blocks pop-ups the tool tells you how to allow them and re-opens only what is left.
Nothing is installed on your WordPress install. ID lookup uses the public REST API; you only need to be logged in to actually edit.
Keep the URL sets you edit often in your browser, and export every URL, ID, type and status to CSV for your records.
Editing a page in WordPress or Elementor means being in wp-admin, not on the live URL. To get there you normally open the page, find it in the Pages list, hover for the post= number, and click through to the editor — for every page, every time. Across a dozen landing pages that is a dozen rounds of the same clicking.
This tool collapses that into one step. Editor URLs are completely predictable: /wp-admin/post.php?post=ID&action=elementor opens the Elementor canvas, and &action=edit opens the standard editor. The only missing piece is the ID — which the WordPress REST API will hand back for any public URL. So you paste the URLs you already have, the tool fills in the IDs, and every page opens in the editor you chose.
The same page can be opened two ways. Elementor loads the visual builder for pages built with it; the WordPress editor (action=edit) loads Gutenberg or the Classic editor, which is where you manage the title, template, SEO fields and the page settings Elementor doesn't own. Choose the one you edit in — or Both when you genuinely need each page open in each.
Open your site's /wp-admin in the same browser and sign in. The editor links only work while you have an active WordPress session — otherwise the opened tabs land on the login screen.
Drop one URL per line into the box above — up to 100 at a time. Choose Elementor, WP Editor or Both, and set a tab delay if you like.
The tool resolves every ID, then opens each page in the chosen editor. If your browser blocks the burst of tabs, allow pop-ups for this page and click Open editors to open the rest.
Tip: the first time a run opens tabs, your browser will likely ask about pop-ups. Choose “Always allow” for this page once and every future run opens cleanly — this is the single thing that makes bulk opening reliable.
A reference for every control — the editor modes, the delay, the pop-up gate, and how to recover the pages a blocker stopped.
The three chips under the box choose what opens. Elementor (the default) opens each page at post.php?action=elementor. WP Editor opens action=edit, the standard editor. Both opens two tabs per page. The mode also decides which buttons appear on each result row.
The slider (0.3–3s) sets the gap between opening tabs. A slower pace is gentler on the browser and, on some setups, less likely to trip the pop-up blocker. It only affects the bulk Open editors action, not the per-row buttons or the ID lookup.
Because opening many tabs is exactly what pop-up blockers stop, the tool tests pop-ups when a run starts. If they are blocked it shows browser-specific steps to allow them; once you have, the un-opened pages stay marked so you can pick up exactly where it stopped.
post or page.The Open editors button in the results header (re)opens every found page in the chosen mode — click it after allowing pop-ups. Each row also has its own Elementor and WP links and a Copy button for the ID, so you can open a single page on demand without a bulk run.
When a run finishes with any Not found or Blocked rows, a Retry failed button appears and re-resolves only those URLs, leaving your successes untouched. Blocked is often a temporary proxy or rate-limit hiccup, so it is worth a click.
Name the URLs in the box and hit Save URLs to keep them for later — handy for pages you re-edit every month. Click a saved list to load it, or the bin icon to delete it. Lists live in this browser's localStorage: they survive a refresh but never reach our servers and won't follow you to another device.
If a site lives under example.com/blog/ rather than the root, its REST API and wp-admin sit under that folder too. The tool checks the root first, then the first path segment, and points the editor links at the base that actually answered — so these resolve without you doing anything.
If an opened tab shows the WordPress login screen, you weren't signed in to that site. Log in once in any tab, come back, and click Open editors again — the session is shared across tabs, so the rest will open into the editor.
Copy all IDs puts every found ID on your clipboard as a newline list; Export CSV downloads the full table (URL, ID, type, status) for spreadsheets and audits. Per-row Copy grabs a single ID.
Everything runs in your browser. There is no SerpHammer backend, nothing you paste is stored on our servers, and saved lists stay in this browser's own storage. URLs go to the target site's REST API and — only when a direct call is blocked — to the public corsproxy.io. Only public URLs are ever sent; never credentials.
Install the tool as an app from your browser menu (or the prompt that appears) and it opens in its own window and works offline. The tool itself is offline-capable; live sites and their REST APIs still need a connection to reach.
Paste the normal page URLs into the box at the top of this page, one per line, choose Elementor as the editor, and click Fetch IDs & open. The tool reads each slug, looks up the post ID from the site's WordPress REST API, then opens every found page in the Elementor editor in its own browser tab. You do not need the post IDs and you do not need to install a plugin.
To look up IDs, no — that uses the public REST API. To actually edit, yes: the editor links point at /wp-admin/post.php on the target site, so you must be logged into that WordPress site in the same browser. If you are not, WordPress will show its login screen in the opened tab. Log in once and re-open the pending pages.
That is your browser's pop-up blocker. Opening many tabs at once is exactly what pop-up blockers stop, so the browser usually lets the first through and blocks the rest. The tool detects this, shows you how to allow pop-ups for this page, and leaves the un-opened pages marked so you can allow pop-ups and click Open editors again to open only what is left.
Elementor opens each page at post.php?action=elementor, i.e. straight into the Elementor canvas. WP Editor opens post.php?action=edit, the standard WordPress (Gutenberg or Classic) editor. Both opens two tabs per page, one of each. Pick the one you actually edit in — Both is only useful when you genuinely need each page open in two editors.
Not found means the REST API answered but had no page or post matching that slug — it may be a draft, a custom post type not exposed to the API, or the slug in the URL differs from the stored one. Blocked means both the direct request and the public CORS proxy fallback failed, usually because the site disabled its REST API through a security plugin or sits behind bot protection. Use Retry failed, or paste the URL into the address bar to confirm it resolves.
Yes, it is completely free with no sign-up. The lookup runs entirely in your browser — there is no SerpHammer backend, nothing you paste is stored on our servers, and saved lists stay in this browser only. The URLs go to the target WordPress site's own REST API, and — only when a direct request is blocked — to the public corsproxy.io service, which then sees that URL. Only public URLs are ever sent, never any credentials.
Paste the URLs, pick an editor, and land in wp-admin ready to edit. Free, instant, no plugin.
Open the bulk editor
Install Bulk Page Editor
Add it to your desktop or home screen — it opens in its own window and keeps working offline.