A practical web toolkit
Pro SEO Tool.
Less busywork.
ProSEO brings your everyday SEO tasks into one free toolkit: review pasted HTML, preview search snippets, build campaign links and clean URL or CSV lists.
Destination URL
Source
Medium
Ready to track
example.com/spring-collection/?
utm_source=newsletter&utm_medium=email
&utm_campaign=spring_launchThe tool directory
Free SEO and marketing tools
Choose the task you need to finish. Each tool includes an example and clear limits.
On-Page SEO Checker
Review pasted HTML in one report: metadata, headings, links, images and JSON-LD syntax. Export CSV or JSON.
Open on-page checkerBulk URL Cleaner
Remove selected tracking fields from URL lists. Preserve functional query text and export the decisions.
Open URL cleanerJSON-LD Inspector
Inspect JSON syntax, literal types and connected ID references in pasted JSON-LD. Export the inventory.
Open JSON-LD inspectorRobots Meta & Canonical Checker
Review robots directives and canonical conflicts in pasted head tags. Export a CSV for follow-up checks.
Open head tag checkerHTML Link Analyzer
Review pasted HTML links, labels and section targets. Export a clear CSV inventory.
Open link analyzerBulk SERP Preview
Compare titles and descriptions, preview desktop or mobile layouts, and review a batch of page data.
Bulk UTM Builder
Build a batch of campaign URLs with consistent source, medium and campaign values. Export ready-to-use links.
Redirect Map Checker
Review a planned URL migration for loops, repeated sources and chains before implementing your redirects.
Robots.txt Rule Tester
Test a pasted ASCII rule set against a URL and see the matching rule, group and line number.
XML Sitemap Validator
Inspect XML structure, missing locations and repeated URLs. Export the locations for a separate live audit.
URL Encoder & Decoder
Encode a query value or decode percent-encoded text without confusing a full URL with a URL component.
Meta Tag Generator
Count title and description characters, then generate escaped HTML tags for metadata, canonical URLs and Open Graph sharing.
Heading Outline Checker
Extract H1–H6 headings from pasted HTML and review empty headings, repeated H1s and jumps in the outline.
Word & Reading Time Counter
Count words, Unicode characters, paragraphs and lines, with an estimated reading time at the speed you choose.
Bulk Slug Generator
Turn titles into lowercase URL slugs, retain non-Latin letters and flag collisions within a batch.
CSV Cleaner & Deduplicator
Trim cell edges, remove blank records and exact duplicate rows, while preserving quoted commas and multiline values.
No matching tool. Try “URL”, “CSV” or a different category.
Workflows, explained
Make the result useful.
A tool gives you an output. These guides help you decide what to do with it.
Keep UTM names consistent across a campaign
Plan source and medium values before building links, then check them in the same report.
Read the workflow →What a title preview can—and cannot—tell you
Use the mockup to review clarity without treating its width estimate as a ranking score.
Read the workflow →Review your redirect map before a migration
Find conflicting destinations and loops while the changes are still easy to correct.
Read the workflow →Latest practical articles
Bing URL Submission vs IndexNow: Choose the Right Method
Choose a notification method, review a six-URL example and distinguish successful delivery from indexing.
Choose a submission method →Rich Results Test vs Schema Markup Validator: Which Check?
Understand syntax, vocabulary and Google eligibility with a worked example and current FAQ feature guidance.
Choose the right validation check →Shopify SEO Tools: A Practical Store Checklist
Review a small store with native controls, a concrete issue log and checks for discovery, markup and redirects.
Use the store checklist →Semrush AI Visibility Toolkit: What It Measures
Separate mentions, citations and audience estimates, with current access limits and a fictional review log.
Understand the AI metrics →Sitebulb vs Screaming Frog: Which Fits Your SEO Audit?
Choose a crawler using rendering needs, reporting, plan limits and a repeatable shop-audit example.
Compare the audit workflows →Ubersuggest vs Semrush for Keyword Research
Compare keyword ideas, competitor gaps and export allowances, then map a shortlist to useful pages.
Choose a research workflow →How to Use Ahrefs SEO Toolbar for On-Page Checks
A flawed HTML example and a short issue log turn a toolbar inspection into publishing decisions.
Read the Ahrefs Toolbar guide →Free Ahrefs Alternatives: A Practical Workflow for Small Sites
Six free options mapped to their useful tasks, access limits and a worked small-site review.
Read the free alternatives workflow →Search Console Keyword Analysis: Choose the Right Page to Improve
A four-query teaching example shows how to connect search evidence to a useful page update.
Read the keyword analysis guide →XML Sitemap Validation: Review Six Entries Before Submission
A six-entry XML sample separates duplicate-location checks from live URL and indexing decisions.
Read the sitemap validation guide →How to Remove UTM Parameters from URLs in Bulk
Follow a tested eight-URL batch, review protected links and duplicates, then export a CSV review or TXT list.
Read the bulk UTM removal guide →How to Inspect JSON-LD Before Publishing: Types, IDs and Syntax
A seven-object graph and a malformed second block explain syntax, shared IDs and follow-up checks.
Read the JSON-LD review guide →How to Check Noindex and Canonical Tags Before Publishing
A four-tag example explains restrictive Googlebot rules, conflicting canonical targets and the next live checks.
Read the head tag review guide →How to Review Internal Links from a Page’s HTML
A tested nine-link example shows how to review destinations, anchor labels and section targets.
Read the internal link review guide →How to Clean SEO CSV Exports Without Losing Useful Rows
A tested CSV example explains exact duplicates, repeated URLs, quoted fields and choosing the right export format.
Read the CSV cleanup guide →Google Trends Keyword Research: Find Useful Long-Tail Topics
A real search-interest comparison, related query examples and a filled brief for choosing a useful page.
Read the keyword research guide →Meta Description Length: Write, Preview and Check Your Snippet
Counted drafts, an original width illustration and a practical workflow for checking the published head tag.
Read the description guide →Free working templates
Download a ready-to-use sheet.
Start with filled examples and clear review steps. Choose a CSV for a focused task, or the Excel workbook for all nine worksheets with editable status dropdowns and progress counts.
Sample data uses example.com and invented campaign values. Replace examples before using a sheet for your own website.
Preview the sheet contents
Keyword research planner
Twelve illustrative keyword seeds include working intent, a candidate page, a research task and the evidence to record. The sheet contains no measured volume, difficulty or trend estimates.
| Keyword seed | Research task | Status |
|---|---|---|
| remove UTM parameters | Compare task and result formats before changing the existing tool page | Not started |
| check noindex and canonical tags | Review the existing guide before proposing a second page | Not started |
On-page SEO review
Twelve invented findings for a sample guide cover purpose, titles, descriptions, headings, examples, links, image text and saved-page checks. Each row includes an intended outcome, action and owner.
| Review area | Invented finding | Status |
|---|---|---|
| Page purpose | The opening does not explain the guide's practical task | Not started |
| Title | The title does not name the guide's subject | Not started |
URL cleanup decisions
Twelve filled examples distinguish reference copies, measured campaign links, functional fields and protected access URLs. All statuses start as Not started. Use them with the Bulk URL Cleaner.
| Scenario | Review decision | Status |
|---|---|---|
| Search and repeated filters | Keep q and both tag fields; review UTM removal | Not started |
| Signed access URL | Keep the complete URL; ask its owner | Not started |
Structured data review
Twelve filled review steps separate JSON syntax, shared identifiers, visible facts and live tests. A parsed block is not a schema validation pass. Use the JSON-LD Inspector for the supplied sample.
| Step | Example finding | Status |
|---|---|---|
| Shared identifier | Two descriptions use the same organization ID | Not started |
| Mixed HTML example | One JSON block parses and one has a trailing comma | Not started |
Head tag review worksheet
Twelve filled examples cover robots directives, canonical targets and the follow-up checks that need a live page. All statuses start as Not started. Use it with the head tag checker.
| Check | Example finding | Status |
|---|---|---|
| Generic robots | index, follow, max-snippet:160 | Not started |
| Googlebot-specific rules | noindex, nofollow | Not started |
Content brief planner
Ten illustrative briefs include a query, intent, proposed path, original contribution and evidence to collect. The queries are examples, with no search-volume or trend estimates.
| Topic | Primary query | Status |
|---|---|---|
| Noindex review | check noindex tags | Not started |
| Canonical targets | conflicting canonical tags | Not started |
Campaign naming worksheet
Columns: destination URL, source, medium, campaign, content, optional term, owner, reviewed and notes. Leave term empty when keyword tagging is not needed.
| Source | Medium | Campaign | Content |
|---|---|---|---|
| newsletter | website_launch | hero_button | |
| newsletter | website_launch | body_link |
Redirect mapping sheet
The CSV contains exactly two columns, from_url and to_url, so it can be pasted into the Redirect Map Checker. The Excel version also includes reason, owner, deployment and verification fields.
| from_url | to_url |
|---|---|
| /serp-preview/ | /bulk-serp-preview/ |
| /title-checker/ | /meta-tag-generator/ |
Before-publishing checklist
Each row includes a review criterion, how to check it, a status, an owner role and a useful note. The checklist starts as Not started; it is ready for your own review.
| Check | How to check | Status |
|---|---|---|
| Page purpose | Read the opening and compare it with the page's main action. | Not started |
| Original value | Identify the specific information a visitor can apply. | Not started |
| Factual accuracy | Check named sources and repeat important instructions yourself. | Not started |
Our approach
Useful outputs.
Clear boundaries.
ProSEO focuses on everyday publishing and website tasks. The tools explain what they check, what they leave out and where a manual review still matters.
Practical by design
Examples, CSV exports and simple inputs help you finish a real task.
No invented scores
Outputs describe specific checks rather than a made-up Google ranking score.
Local input processing
The utilities process pasted text and files in your browser.
Limits in plain language
A saved-rule test and a live website audit answer different questions.
Build URLs from the destinations you enter. Existing UTM values are replaced; other query parameters and fragments are kept. No website is fetched.
This is a layout estimate. Google may rewrite a title or description. Width measurements use 20px Arial and are not fixed Google limits.
This checks your planned mapping. It does not request live URLs, verify HTTP responses or install redirects. Paths are resolved against your base site.
A basic pasted-rule simulator for ASCII paths without percent encoding. It selects an exact crawler token group, or the * group, and supports path prefixes, * and $. This is not a live crawl or indexing check.
For live crawl behavior and encoded paths, consult Google’s robots.txt specification. Crawl permission does not confirm indexing.
Checks pasted XML structure and locations. It does not test live status codes, canonicals, robots rules or indexability. This tool accepts up to 1 MB and 5,000 entries per check.
Choose whether you are editing one parameter value or a complete URL. Decoding does not treat + as a space; this is URI decoding, not HTML form decoding.
Character counts and the title-width estimate are editing aids. This generates tags from your inputs; it does not check a live page or predict Google’s chosen snippet.
Paste HTML, not a page URL. The sample is parsed in an inert template: pasted scripts are not executed, resources are not loaded and the HTML is not inserted into the visible page. Maximum 1 MB and 1,000 headings.
Use plain text. HTML tags would be counted as text, so remove markup first. Characters are Unicode code points; a visible emoji or combined letter can contain several code points. Maximum 100,000 characters.
One title per line, up to 500 titles. Latin accents are simplified, apostrophes removed and punctuation replaced by hyphens. Non-Latin letters and marks are retained. This does not check whether a path already exists on your website.
Load up to 1 MB and 5,000 data records plus one header. Completely blank records are removed. All remaining records must have the same number of columns. Automatic detection uses the first non-empty record; choose a delimiter explicitly if the preview looks wrong.
Choose the names before building the links
A campaign becomes difficult to report on when one person uses newsletter, another uses Newsletter and a third uses weekly_email for the same source. Decide on a short naming convention and keep it in the campaign worksheet before you distribute the first link.
In a simple email launch, use the source for the sending publication, the medium for email and the campaign for the specific launch. Use content when you need to distinguish two placements, such as a hero button and a text link. These are examples rather than rules for every organization.
Review one real destination first
- Open the destination page normally and confirm it is the page the campaign promises.
- Add a single destination to the UTM builder and complete the three required fields.
- Inspect the generated URL. Existing non-UTM parameters and its fragment should remain intact.
- Open the link yourself and confirm that the site’s analytics records the campaign as expected.
- Generate the rest of the batch only after this check passes.
Keep a record of what changed
The builder replaces existing UTM fields on a destination. That is useful when rebuilding a campaign but can overwrite another team’s tagging. Save the original URL alongside the final URL, label the export with the campaign and date, and agree on which version will be sent.
A correctly constructed URL does not prove that analytics is installed, that consent permits measurement or that every visit will be recorded. Check those details in your own analytics setup. Avoid using campaign tags for routine internal navigation unless you have deliberately planned how that affects attribution.
Review clarity before width
A title preview is useful for spotting an awkward phrase, a repeated brand name or a subject that appears too late in the line. Start by asking whether a reader can tell what the page helps them do. A title such as Website Help is short, but WordPress Sitemap 404: Check These Settings describes a specific problem.
The preview estimates a familiar search-result layout. It cannot predict the exact words or presentation Google will select. A narrow letter and a wide letter use different amounts of space, so a character count is only part of the editing decision.
Compare related pages in a batch
- Export or assemble the URL, title and description for each page you want to review.
- Quote CSV text that contains commas and keep one page per row.
- Check repeated titles first. Decide whether the pages serve different tasks or need consolidation.
- Review missing descriptions and wide titles in the context of the actual page.
- Change the source metadata in your publishing system, then confirm the live page reflects the edit.
Do not mistake the mockup for a live audit
A tidy preview does not confirm that your page is indexed, that the title tag exists in its rendered HTML or that the page ranks for a query. This tool examines the text you supply. Use Search Console and the live page when checking those other questions.
For the distinction between a supplied title and Google’s title link, see Google’s title-link guidance.
Make the mapping explicit
A redirect plan should connect each old URL to a relevant replacement. Use a sheet with one source and one destination per row. If the old page has no useful replacement, record that decision separately rather than mapping every retired page to an unrelated homepage.
Enter the correct base domain when your sheet uses paths such as /old-guide/. The checker keeps the distinction between /guide and /guide/, because your server may treat them differently. It also preserves query strings.
Resolve conflicts before deployment
- Check repeated sources. The same old URL should not have two competing destinations.
- Remove self redirects and loops, including loops that pass through several intermediate URLs.
- Review chains. Where appropriate, map the old URL directly to the final relevant destination.
- Confirm that the replacement page exists and answers the visitor’s original need.
- Save the reviewed map and a record of where it will be implemented.
Test the live responses afterwards
The map checker follows only the rows you provide. It cannot see a web server rule, a CMS setting, a CDN redirect or a destination that is unavailable. After implementing the map, test representative old URLs and inspect the actual response and final destination.
Update internal links to the final URLs so visitors do not rely on redirects for everyday navigation. Revisit the sitemap and other references that still use retired addresses. Keep a recovery copy of the original mapping and configuration in case a live test exposes an unexpected result.
ProSEO is an independent toolkit for routine SEO, campaign preparation and website housekeeping. Its purpose is to turn a specific input into an understandable output, with enough explanation to help you use that output responsibly.
How the tools work
The utilities on this page process the text you enter in your browser. They do not perform live site crawls, retrieve search volumes or query backlink databases. CSV reviews and rule tests are limited to the data you provide.
How to judge an output
Each tool explains its scope beside its inputs. Use sample data to learn the workflow, then compare the result with the original source and, where relevant, the live website. A result is a practical check, not a ranking guarantee or a substitute for all other verification.
On-Page SEO Checker: reviews supplied HTML within 1 MB, 5,000-element and 2,000-link limits. It does not fetch URLs, execute supplied scripts, validate live responses or establish indexing. Counts and prompts are not a ranking score.
Bulk URL Cleaner: removes selected query names from up to 2,000 supplied URL lines. It preserves remaining raw segments, leaves recognized access URLs unchanged and does not test destinations or measurement.
JSON-LD Inspector: parses supplied blocks and inventories literal @id/@type objects. It does not expand contexts, validate Schema.org requirements or establish Google eligibility.
Robots Meta & Canonical Checker: reviews up to 500 KB and 2,000 relevant tags from a head fragment. Its Googlebot index/follow summary and canonical URL inventory do not establish live headers, tag placement or indexing.
These utilities are intended for routine preparation and review. They cannot guarantee rankings, traffic, indexing or advertising approval.
HTML Link Analyzer: reviews up to 1 MB and 2,000 supplied HTML anchors, with destination resolution and same-page section checks. It does not request URLs, verify HTTP status or perform a complete accessibility audit.
- The SERP preview is an approximate layout using supplied text.
- The UTM builder constructs URLs; it does not verify analytics collection.
- The redirect checker evaluates the supplied mapping, not live HTTP behavior.
- The robots tester supports basic ASCII rules and exact bot-group selection, with a wildcard fallback. Encoded paths and other crawler-specific behavior are out of scope.
- The sitemap validator checks XML and locations, not whether those URLs are indexable.
- The URL utility transforms URI text and does not assess the safety of a destination.
- The meta generator creates HTML from supplied fields and does not inspect a live page or promise a search snippet.
- The heading checker reviews pasted HTML, not live JavaScript, CSS visibility or the full accessibility tree.
- The word counter reports text quantities; reading time uses the speed you select and is not a quality score.
- The slug generator flags collisions within the supplied batch, not paths already used on your website.
- The CSV cleaner compares complete records after the selected trimming. Export formats differ in how they treat formula-like cells.
Review outputs before changing a live website. Keep a recoverable copy of the original configuration when applying redirects or crawl rules.
Tool inputs
The utilities included in this page process pasted text and template data locally in your browser. Their scripts do not send those inputs to an external API, store them in browser storage or add them to an analytics event.
Page requests and your downloads
If this page is hosted online, loading it still creates normal requests to that website and its hosting infrastructure. The host may keep access logs. Other features of the host site, including login, comments, analytics or advertising, need their own accurate privacy notice.
Exported files are created when you choose a download. You control where they are saved and how they are shared. Avoid entering passwords, private tokens or personal information in utility inputs.
When you leave this page
Links to external documentation lead to separate websites. Their data practices are independent of this toolkit.