| 4:03 pm on Jun 4, 2012 (gmt 0)|
The * used in this way is not a Regular Expression, so be careful how you talk about it.
If you want to include directives that are intended for specific search engines, you can use any syntax that they say they recognize. But if you want an all-purpose "Which part of 'disallow' didn't you understand?" then stick to the minimalist form.
I don't know about Bing, but google ignores "crawl-delay" even though I'm sure it understands it perfectly well.
| 4:57 pm on Jun 4, 2012 (gmt 0)|
Yea I was talking about like a page that was page.aspx then the page had page.aspx/color=black and so on for more refinements. So I was going to add
Disallow: /page.aspx* does this sound correct?
| 5:27 pm on Jun 4, 2012 (gmt 0)|
Never use * at the end of the pattern. The pattern "matches from the left" and is a "prefix match".
Use * only near the beginning or in the middle of the pattern.
Disallow: /this disallows anything beginning
example.com/this so the
* is not needed.
Disallow: /*that disallows URL requests like
example.com/<something-or-anything>that as a prefix.
$ ending is needed only when you need an exact match.
| 5:41 pm on Jun 4, 2012 (gmt 0)|
Thanks for the update g1smd. However with the example I put above I would need to match whatever is after the page.aspx and there isnt a real end that I can put on it because it is dynamic. So the page could be
Is there a way to match what I am talking about above with the *? thanks!
| 5:47 pm on Jun 4, 2012 (gmt 0)|
Do you need to match some query strings and not others?
Is this for one particular aspx page or for all aspx pages?
If you need to block all query strings for one particular
.aspx page then the prefix match for disallowing
It's a prefix match. You dont need a
If you want to block any
.aspx page with any query string, e.g. block
example.com/<anything>.aspx?<anything> then use:
* is needed only in place of the page name.
* at the end of the pattern.
* only near the beginning or in the middle of the pattern.
If you wanted to block requests for exactly
example.com/page.aspx without query strings but allow the same page with query strings you would use
| 6:37 pm on Jun 4, 2012 (gmt 0)|
Thanks g1smd I think I understand now. Since it is all query strings that go with page.aspx then I will use Disallow: /page.aspx? and it will match all of the additional query stings added to it. Correct?
Thanks again I really appreciate your help!
| 6:42 pm on Jun 4, 2012 (gmt 0)|
The pattern is a prefix match (matches from the left) so the rule
matches any request that BEGINS
example.com/page.aspx? with anything or nothing after the question mark.
| 6:52 pm on Jun 4, 2012 (gmt 0)|
Thanks g1smd you have really helped a lot!
| 7:48 pm on Jun 4, 2012 (gmt 0)|
The devil is in the details.
It's especially important to define "exactly" what you want to do in plain English before you even begin to think about any code.