Is anyone else getting Google crawl errors using wblink?

[MissyW]

I have started using wblink internal page links intensively since upgrading my site to wb 2.8.2 - they are so convenient!  But now Google has starting reporting crawl errors  .  Strangely, Google is reporting a relative path to the url, e.g.

Code:

http://www.mydomain/pages/menu-title/wblink73

- where menu-title is the menu where the embedded internal link is sitting in the content.  Page 73 sits in a different menu.

So Google is getting the link url quite wrong. And I don't understand why it is including "wblink73" literally in the link and not the interpreted page file name (page-name.php). Could it be anything to do with the fact that I have added a title to the internal link, e.g.

Code:

<a title="free consultation" href="[wblink73]">

Could it be that I may have copied and pasted the html code for the link, rather than clicking the website baker link button?? I am puzzled as to why no one else is reporting this problem

[NorHei]

First thing i got in mind is that you check the date of the crawl errors , here in my account i still have some pretty old crawl errors that no longer apply.
Next step may pe check the page if the problem is still there. (check sourceview in browser)
Another possible cause may be that if you (or your provider) uses the google sitemap tool for submitting sitemaps. The sitemap sool scans all source files in your directories submitting them to google.

It would be far more easy to say something more precise if you post the google crawling protocol and the page. 

[MissyW]

First thing i got in mind is that you check the date of the crawl errors , here in my account i still have some pretty old crawl errors that no longer apply.

Yes, isn't that true.  I have some really outdated ones too.  But these ones I am talking about are current.

Next step may pe check the page if the problem is still there. (check sourceview in browser)

Brilliant!   I wouldn't have thought of this - I was previously just checking the html code via the wb backend .... but on checking the sourceview via the browser as  you suggested, viola!, there was the <a href="[wblink73]"> reference in the source code.  I have discovered the origin of the problem was in embedding a wblink in a droplet which I created for repetition on a number of pages.  Seems like you musn't use a wblink in a droplet(!?) I have replaced it with an absolute url address, and all is fixed.

Another possible cause may be that if you (or your provider) uses the google sitemap tool for submitting sitemaps. The sitemap sool scans all source files in your directories submitting them to google.

You are full of interesting comments, though I am getting a bit out of my depth here.  I have submitted google_sitemap.php (author Karelkin Vladislav version 1.5) to Google.  This is a WB sitemap so I am guessing it should not be causing any problems.  I have checked the sitemap via Google's 'see sitemap' in webmaster tools, and all the links are correct.

It would be far more easy to say something more precise if you post the google crawling protocol and the page.  

Thank you for such a thoughtful reply to my post!   My problem is solved and I take it you no longer need my page url, but please tell me if you do.