Support » Fixing WordPress » How to automatic replace dash with space in permalink ?

  • Resolved Sinac

    (@sinac)


    Hi , Search engine like Google have a law for dash , means NOT
    ex: wordpress -codex –means–> Search wordpress But don’t show pages that have codex
    if we automatically replace – with %20 can more seo sites.
    may this information cat help you:
    wp-admin/post.php
    wp-admin/edit-form-advanced.php

Viewing 4 replies - 1 through 4 (of 4 total)
  • I’m not sure where you think the issue is. From Google’s pov, ‘wordpress -codex’ is not the same as ‘wordpress-codex’. It is perfectly OK to use hyphens in post/page urls.

    ok, it’s true; thanks
    In other words I like to show Space in my urls
    are you have a any idea?

    Spaces in urls are a really Bad Idea – which is why WP replaces them with hyphens.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Plugin Review Team Rep

    Spaces in URLs are not universally accepted by browsers, OS, or servers. Or apps.

    Basically, the space is not a legal character in URLs.

    Long version: http://www.ietf.org/rfc/rfc1738.txt

    Unsafe:

    Characters can be unsafe for a number of reasons. The space character is unsafe because significant spaces may disappear and insignificant spaces may be introduced when URLs are transcribed or typeset or subjected to the treatment of word-processing programs. The characters “<” and “>” are unsafe because they are used as the delimiters around URLs in free text; the quote mark (“””) is used to delimit URLs in some systems. The character “#” is unsafe and should always be encoded because it is used in World Wide Web and in other systems to delimit a URL from a fragment/anchor identifier that might follow it. The character “%” is unsafe because it is used for encodings of other characters. Other characters are unsafe because gateways and other transport agents are known to sometimes modify such characters. These characters are “{“, “}”, “|”, “\”, “^”, “~”, “[“, “]”, and “`”.

    All unsafe characters must always be encoded within a URL. For example, the character “#” must be encoded within URLs even in systems that do not normally deal with fragment or anchor identifiers, so that if the URL is copied into another system that does use them, it will not be necessary to change the URL encoding.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘How to automatic replace dash with space in permalink ?’ is closed to new replies.