دليل SEO البزاقة وأفضل مولدات البزاقة السائبة

An SEO slug is the human-readable part of a URL that identifies one specific page, and it is one of the few on-page elements you set once and rarely revisit. Get it right and it quietly helps readers, crawlers and anyone pasting your link into a chat window. Get it wrong and you inherit duplicate URLs, broken redirects and link rot that outlives the content itself.

It also attracts more folklore than almost any other SEO topic. You will read that slugs are a major ranking factor, that they must be exactly three to six words, or that search engines weigh some fixed list of two hundred signals. None of that comes from Google. What Google actually publishes is narrower and more useful, and this guide sticks to it, then covers the mechanics that genuinely bite: casing, encoding, redirects and generating slugs in bulk without introducing collisions.

What a URL slug actually is

The slug is the final, descriptive segment of a URL path: the part that names this page rather than the site or the section. Take a clean example and break it apart.

https://example.com/blog/best-football-stadiums-london

Part	Value	What it does
Scheme	https://	The protocol; HTTPS is expected on any modern site
Host	example.com	Domain and top-level domain
Path segment	/blog/	The directory or section the page sits in
Slug	best-football-stadiums-london	The unique, readable identifier for this page

Note what the good version does not contain: no spaces, no capitals, no commas, no trailing punctuation. Spaces are not legal in a URL and get percent-encoded into %20, which is why a hand-typed slug with gaps renders as a broken-looking link. To inspect a URL that has already been mangled, a URL parser splits it back into its parts, and a URL encoder shows how a character will be transmitted.

What Google actually says about slugs

Start with the claim most likely to mislead you. Google's own SEO Starter Guide is explicit about how much ranking weight URL keywords carry:

From a ranking perspective, the keywords in the name of the domain (or URL path) alone have hardly any effect beyond appearing in breadcrumbs.

That is the most important line here. Slugs are worth doing well, but not because stuffing a keyword into the path moves you up the results. The same guide recommends including words in the URL that may be useful to users, and contrasts a descriptive URL with one built from random identifiers: a usability argument, not a ranking one.

The often-repeated figure that search engines use "over 200 ranking factors" is not something Google publishes or maintains; it is a number that escaped into SEO folklore years ago and has been repeated ever since. Treat it as a slogan, not a specification.

Here is what Google's URL structure documentation does state, and each point has a practical consequence.

Use hyphens, not underscores

Google recommends hyphens rather than underscores to separate words in URLs, on the grounds that it helps users and search engines identify concepts. Underscores historically signalled that terms belong together, as in a function name. This is one of the few slug conventions with direct documentation behind it, so follow it without debate.

URLs are case sensitive, and that creates duplicates

Google's documentation states plainly that Search's URL handling is case sensitive, so /apple and /APPLE are treated as two different URLs. On a case-insensitive server, both can serve the same page, and you end up with two addresses for one piece of content competing for the same signals. Standardise on lowercase everywhere and enforce it at the server level with a redirect rule. If you are cleaning up an inherited set of mixed-case paths, an uppercase to lowercase converter will normalise the list before you generate the redirect map.

Percent-encode anything outside ASCII

Google advises using percent encoding in link href attributes where necessary, with characters outside the ASCII range requiring it. Browsers display the decoded form, so an accented or non-Latin URL still reads correctly while travelling safely on the wire. What matters is linking to it consistently.

Write in your audience's language

The documentation recommends using words in your audience's language in the URL, and transliterated words where that applies. If you run localised sections, do not leave every slug in English by default just because it is easier for your team to read the CMS.

Avoid overly complex, parameter-heavy URLs

Google warns that overly complex URLs, especially those with multiple parameters, can create unnecessarily high numbers of URLs for crawlers, wasting bandwidth and leaving parts of a site unindexed. This is the real technical argument for clean slugs: not that they rank better, but that a sprawling parameter space is expensive to crawl. If you want a quick read on how your paths are shaped across a site, run a sample through a URL structure analyzer.

Group related pages in directories

Grouping similar topics into directories helps Google learn how often the URLs in each directory change, according to the same documentation. A tidy /blog/, /docs/ or /products/ prefix is doing more work than the slug itself.

How to write a slug: a working checklist

Work through these in order when you create a page. Most of them take seconds and none of them can be fixed cheaply after the URL is public.

1. Start from the page title, not the keyword list. Strip the title down to the words that identify the topic. If a reader could guess the page content from the slug alone, you are done.
2. Lowercase everything. Then add a server rule that redirects any uppercase variant to the lowercase form, so a stray capital in someone else's link never creates a second URL.
3. Separate every word with a hyphen. Never run words together and never use underscores; medical-grade-skincare is readable, medicalgradeskincare is not.
4. Remove stop words only when the slug still reads naturally. Trimming "the" and "of" is fine; trimming until the phrase is nonsense is not. Readability is the whole point.
5. Keep it short, but do not obsess over a word count. There is no official length limit. Shorter slugs are easier to read, share and display in search results, and Google truncates long URLs in the results snippet. Aim for the shortest phrase that stays unambiguous.
6. Drop dates, IDs and session parameters. A slug like /post-10 tells nobody anything, and embedding a year means the URL looks stale the moment the content is refreshed.
7. Strip punctuation and symbols. Commas, apostrophes, ampersands, emoji and slashes either get encoded into noise or change the path structure. Letters, numbers and hyphens are enough.
8. Do not repeat the directory in the slug. /blog/blog-seo-slugs is redundant; /blog/seo-slugs is not.
9. Check for collisions before publishing. Two titles can slugify to the same string, and most CMS platforms silently append a number. Deduplicate the list first; a duplicate lines remover catches exact repeats in a batch of generated slugs before they reach the database.
10. Clean the source text first. Titles copied from a spreadsheet arrive with stray line breaks and double spaces, so clearing line breaks for readability and SEO comes first, and a text separator splits a pasted block into one title per line.

Changing a slug without losing what you built

An existing URL that ranks and has links pointing at it is an asset. Changing it is never free: every inbound link, bookmark and internal reference points at the old address, and search engines have to be told where the page went.

If you decide to change one, do it in this order. Publish the page at the new slug. Put a permanent server-side redirect from the old URL to the new one, which is the standard signal that a page has moved for good and the way accumulated link value is passed along. Then update every internal link that pointed at the old path, because leaving them to bounce through a redirect wastes crawl budget and slows users down. Finally, resubmit or regenerate your sitemap so the new URL is discoverable directly.

The mechanics are straightforward on an Apache stack: the Htaccess URL Redirect Generator writes the rules for you, and a redirect checker confirms afterwards that each old URL returns a single permanent hop to the new one rather than a chain or a loop. Chains are the most common failure here: a slug changed twice, with the first redirect never updated, leaves crawlers walking two or three hops to reach the content.

After the change, sweep for anything you missed. A broken link checker finds internal references still pointing at the retired path, and an XML sitemap generator rebuilds the file with the current set of URLs. Expect some ranking movement while the change settles; that is normal, and it is a reason to batch slug changes rather than trickle them out. Older domains with established link profiles have more to lose from careless URL churn, which is part of why domain age matters for SEO in the first place.

Slugs, titles, meta descriptions and Open Graph

The slug is one of the few things a searcher sees before deciding to click, alongside the title, the description and, on social platforms, the link preview. They need not be identical, but they should describe the same page in the same terms.

A coherent set looks like this: the slug /meta-tags-for-seo, the title "How Meta Tags Improve Your SEO Ranking", and a description explaining how to use meta tags and SEO-friendly slugs to improve visibility. A reader scanning the result gets the same answer from all three. To audit what your pages are actually emitting, a meta tags analyzer reads back the tags a crawler receives, which is often not what the CMS preview promised.

Open Graph tags and the shared link

Open Graph tags control how Facebook, LinkedIn and X render a link preview: the title, description, image and canonical URL. They have no direct effect on Google rankings. What they affect is whether a shared link looks trustworthy enough to click, and a readable slug such as /seo-slug-generator is visibly more clickable than /tool123.

Keep the OG title and description aligned with the meta title and description so the same page does not present two different identities depending on where it was shared, and verify the markup with an Open Graph checker rather than trusting that the plugin got it right.

Bulk slug generators worth knowing

Generating slugs one at a time is fine for a blog post. It is not fine for a product catalogue, a migration or a backlog of several hundred titles, where consistency matters more than craft and one manual typo becomes a permanent URL. Bulk generators take a list of titles and return slugs under a single rule set.

UrwaTools Text to Slug Generator

The Text to Slug Generator converts text, titles or multiple lines into lowercase URL slugs: it strips special characters and extra spaces, replaces spaces with hyphens, and handles multiple lines in one pass. It suits bloggers, developers and content managers who need consistent slugs for a batch of pages without wiring a slugify library into their own build.

CaseConverter.tools Slug Generator

The Bulk URL Slug Generator at CaseConverter.tools states that you can paste multiple lines to use bulk mode, choose a hyphen or underscore separator, optionally remove stop words such as "and", "the" and "of", and optionally strip numbers. It reports a processing summary of total lines, successful slugs and empty lines skipped, which is genuinely useful when you are reconciling a generated list against a spreadsheet.

Slugify.online

Slugify.online is a single-input generator: paste one string, choose a dash or underscore separator, and optionally remove stop words or numbers before copying the result. It is quick for one-off slugs; the page does not advertise multiline or batch processing, so it is not the tool for a migration.

Slugify.org

Slugify.org offers a bulk generator with a "generate all" action, hyphen or underscore separators, a maximum length setting, and options covering case formatting, stop-word removal and accent handling. The length cap is the differentiator when every slug in a large catalogue must stay the same size.

How they compare

Tool	Bulk or multiline	Separator choice	Stop-word removal	Length cap
UrwaTools Text to Slug	Yes, multiple lines	Hyphen	Not stated	Not stated
CaseConverter.tools	Yes, with a processing summary	Hyphen or underscore	Yes, optional	Not stated
Slugify.online	Single input	Dash or underscore	Yes, optional	Not stated
Slugify.org	Yes, generate all	Hyphen or underscore	Yes, optional	Yes, max length

Whichever you use, check the output before it reaches your CMS. Automated slugification is where collisions, truncated phrases and stray transliterations appear, and fixing a URL after publication costs a redirect.

Frequently asked questions

Do keywords in the slug improve rankings?

Barely. Google's SEO Starter Guide states that keywords in the domain name or URL path alone have hardly any effect on ranking beyond appearing in breadcrumbs. Write the slug for the person reading the link, and take the ranking benefit as incidental.

How long should an SEO slug be?

There is no documented limit and no official ideal. Shorter is easier to read, share and display, and search results truncate long URLs, so the practical rule is the shortest phrase that still identifies the page unambiguously. Any specific word count you have read is a convention, not a guideline from Google.

Hyphens or underscores?

Hyphens. Google's URL structure documentation recommends hyphens to separate words and notes that underscores historically indicated terms meant to stay joined. This is one of the few slug rules with explicit documentation behind it.

Does uppercase in a URL really cause duplicate content?

It can. Google treats URL paths as case sensitive, so /apple and /APPLE are distinct URLs. If your server returns the same page for both, you have two addresses for one page splitting their signals. Force lowercase with a redirect rule and the problem disappears.

Should I change old slugs to make them better?

Only when the current URL is genuinely misleading, broken or being replaced as part of a migration. A slug that is merely imperfect is not worth the redirect, the lost internal links and the temporary ranking wobble. When you do change one, redirect permanently and update internal links the same day.

Can I generate slugs in bulk safely?

Yes, with two safeguards. Clean the input first so stray line breaks and double spaces do not produce empty or malformed slugs, and deduplicate the output before import so two similar titles do not collide into the same path. Review a sample by hand; automated transliteration of accented or non-Latin text is where surprises hide.

The short version

Write slugs for people. Keep them lowercase, hyphen-separated, free of punctuation, short enough to read at a glance and descriptive enough to guess the page from. Enforce a single canonical casing at the server, percent-encode anything outside ASCII, and group pages into sensible directories.

Then stop optimising them. The documented ranking effect of URL keywords is close to nothing, and the real wins are elsewhere: not creating duplicate URLs, not breaking links when you move a page, and not letting a bulk import fill your site with collisions. A good slug is infrastructure. Set it once, redirect it properly when it has to change, and spend your effort on the content it points to.