Hot answers tagged

5

This certainly looks like a mistyped URL in the links on pages /blog/page/12/, /blog/page/13/ and /blog/page/14/. On those pages look for a link like the following: <a href='’https://go.example.com/20190620-Lyft-Livestream.html?ref=blog'>Link</a> The erroneous single back curly quote ’ at the start of the URL will trigger the user-agent (...


4

The recommended way to deal with this is to use a 301 ("permanent") redirect from the old article URL to the new article URL. That way users and search engines will be automatically redirected, and you should keep the vast majority of your link equity. That being said, bathing vs feeding a walrus sound like they would have mostly different article contents, ...


4

If you correctly put in 301 redirects and update your sitemap, the site will be fine. However... What are you trying to gain from this change? The Stack Exchange-style hierarchy doesn't make sense for what it seems you're trying to accomplish (a Wikipedia-style website?). What you currently have makes more sense in terms of organizing the information: ...


3

You're right that the form will be submitted to https://squareup.com/mp/login, and that when you just put that URL into a browser, you get a 404. That's because when you type web addresses into a browser, the browser makes a GET request, but the page at https://squareup.com/mp/login is expecting a POST request. GET and POST are HTTP methods. The address bar ...


3

Your question is not clear. Are you trying to block any version of your site? Robots.txt is used to disallow or allow search engines from crawling particular locations of your website. Also, your current config is wrong, use the following: # Paths (clean URLs) User-agent: * Disallow: /admin/ Disallow: /comment/reply/ Disallow: /filter/tips Disallow: /node/...


3

301 redirect the old URL, so that anyone (or anybot) with the old link sees it's been moved. If possible, also add a canonical to the page as an additional confirmation to anyone and anybot that the lowercase version is the right one.


3

Automatic language detection doesn't work well. It is usually based on either the geographic region associated with the IP address or based on the Accept-Language parameter. Geo IP databases are inaccurate for a small (but significant) percentage of users. Probably around 5-10%. Geo IP doesn't work for users that are travelling abroad in a country where ...


3

Two questions in 1 ;) For the first one, redirect example.com/wp to example.com, you must first set your domain to point to the wp directory rather than to its parent directory (www, htdocs...). Then you will have to set the new adress (without /wp) into wordpress Settings via the dashboard or phpMyAdmin (wp_options table). For the second question, at this ...


3

Generally speaking, "hyphen" is prefered over "underscore" - I never had anyone use "periods" before, but for the sake of this question, I recommend hyphens over periods. It is more a readability thing. However, it will neither make or break your site. The only thing that matters when it comes to SEO is that you have a product/service that is needed by ...


3

There is a risk with URL changes of SEO problems, ranking loss, and traffic declines. When correctly implemented with 301 redirects, it can go perfectly fine, but it doesn't always do so. I recommend changing URLs only when there is an overwhelming need. If you do want to change URLs you should consider gentler changes as well: Chang the URL structure ...


2

My bad: My httpd configuration redirects 403 errors to a custom error page, but apparently doesn't report it as an error. Since robots.txt doesn't exist, httpd dutifully did what it was supposed to and returned my custom error page instead. Hopefully this helps someone else.


2

First of all, let me open by saying I personally answered your last question and my proposal was option A. Since I stated my thoughts regarding option A, I will just say why options B and C are no good. Option B uses comma as delimiters for range. Comma is an unsafe character, meaning it will be encoded to %2C in your url and will generally seem like ...


2

rule for all after /page/* redirecting to homepage: RewriteEngine On RewriteRule ^page\/(.*)$ / [R=301,L] or all /page/0-9+/ redirecting to homepage: RewriteEngine On RewriteRule ^page\/(\d+)\/$ / [R=301,L]


2

.html and seo-url/ both looks same for search engines as I know,if them both readable by human. Example : my-seo-url.html my-seo-url/ my-seo-url Here is a nice article to read. https://moz.com/blog/15-seo-best-practices-for-structuring-urls


2

No. It makes no difference. On the contrary, one could argue that shorter and cleaner urls are better than adding the file extension like in this case. This is the same thing that Google says in this vlog.


2

If you want to preserve all URLs from your current website to new website, you can create the URLs in your new website. Preserving URLs: Technically, in terms of SEO, as long as the URL structure is the same, your URLs are always preserved independent of the platform they are in (unless you make a big variation in content, it will not affect your current ...


2

this IP address showing in Google serp does not work If by "does not work", you mean it doesn't resolve (as appears to be the case) then there is nothing you can do. But by the same token, there is nothing you need to do (since SEO is not a concern here) - the IP address will disappear from the SERPs soon enough. I know using the Remove URL tool from ...


2

Your regular expression is pretty close if you remove the $s. Those means "ends with," which isn't what you want. I'd take the approach of having a single "starts with slash" (^/) followed by your dates with parenthesis for grouping, and explicitly say it can end with anything (.* ): ^/((2019/03/01)|(2019/03/02)|(2019/03/03))/.* That should work with ...


2

As stated you should use POST method instead of GET. BUT there's more.. This site is probably using Laravel, because I can see csrf-token in the <head> of the login page (all other pages too of course), so if you stumble upon 422/403/500 or anything other than 404/200 HTTP status codes, you might need to add the _token parameter with the value of the ...


2

# indicates a specific point in the page, an anchor point as they say. Meaning that when you visit the page with the # prefix your screen will automatically scroll to that portion of the page. / indicates a subcategory or page under a category and when you visit it you will start from the top. # Is used only for URL sharing or page formatting when you want ...


2

I'm guessing that your URL change is unrelated to the error. A 500x error usually means a server side processing error, like unable to render the page or there's bug in the server side code on the page (PHP, ASPX, etc). 400x errors typically mean the page doesn't exist. Since Google is showing you a 500 error, are you sure it's because the file doesn't ...


2

There is a few factors you should consider in that case. Keywords in URLs are overrated and don't really have much impact on page ranking. Best practice always keep URLs as short and simple as possible. It is usually a good practice to omit the categories in URL. Because If you decided to change the name of the category for example, then you would also ...


2

i have tried to give the index.php the parameter "page" Although you've not included this in the example you posted - so what you have posted will obviously not work because of this. If your front-controller is dependent on a page URL parameter then you need to pass this in the rewritten URL. For example: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{...


2

There was a bug reported against LiteSpeed HTTPD webserver in 2009. Requesting /408.shtml caused the server to crash. That indicates that there is a bug in that server, and possibly a buffer overflow vulnerability that is remotely exploitable. Those requests against your site are likely to be vulnerability scans looking for installations of LiteSpeed that ...


2

Google does place the language tag in the URL: https://support.google.com/webmasters/answer/182192?hl=de https://support.google.com/webmasters/answer/182192?hl=en https://support.google.com/webmasters/answer/182192?hl=fr But they don’t redirect the variant without the language tag to the variant with the language tag. Instead, they set the variant with the ...


2

It is highly unlikely that Google will consider the within page links indicated with a # as unique pages. Sites like Github have heavy usage of hash links that help with navigation within the page but these links are not indexed by google. The sitelinks guide by Google clearly says We only show sitelinks for results when we think they'll be useful to the ...


2

The #! indication in the URL was used to indicate Google that this section of the page appears on the page after the JavaScript has been executed. For example you have a section on your page example.com/page1#about which makes an AJAX call. In order to make this URL crawlable by Google you had to change this to example.com/page1#!about so that Google ...


2

Google doesn't use keywords in the URL path as a ranking signal much right now (maybe even not at all.) Putting keywords in the URL won't change the SEO directly. It will only change the SEO indirectly through better usability. See Are keywords in URLs good SEO or needlessly redundant? which suggests: Use a few descriptive keywords in the URL path for ...


2

Couple of points to add: 1) Underscores are a JOIN operator 2) Dashes are SEPARATOR 3) Periods are for SUBDOMAINS This is old programming language standards. So all of that is to say, dashes are the way to go. If you use periods your URL will not likely get parsed correctly. Check out the "double-click highlight_test," or was it, "double_click_highlight....


2

Regardless of whether the proposed draft standard specifies that you should encode or not, to answer your specific question... No, it is unlikely to cause a problem if you include both URL encoded (%-encoded) and URL decoded (%-decoded) URLs in robots.txt. One or other will simply get ignored, as one or other simply won't match. UPDATE: To clarify, ...


Only top voted, non community-wiki answers of a minimum length are eligible