: Breadcrumbs good content and good HTML structure I was doing some research on breadcrumbs an came across the following resources: Matt Cutts on breadcrumbs Anna smarty on SEO and breadcrumbs

@Cugini213

I'd recommend changing your breadcrumbs to the human readable lingo because it's human friendly. Also, because shoe-size 6 might be a keyword that people type in Google, as compared to 6. It might help increase your CTR in organic search when someone typing shoe-size 6 matches your site's breadcrumbs.

Vote Up Vote Down

@Lee4591628

There is a good chance that google understands your current breadcrumb method, class, and separators, especially if it mirrors category structure. You could indeed further enhance it with rich data via Schema.org semantics. Here is the Google guide as well as the recommended Schema.org reference. There is also the older "legacy" data-vocabulary reference. Keep in mind, Google will pick and choose which crumbs it shows. It depends on what fits in the tiny horizontal SERP space and what is most relevant to the query.

As far as how the chain goes, def use keywords in a minimal way. I would use neither of your approaches. Pardon any brevity (& opinion), but if there is 1 main parent, it should be called shoes. Then for each child, just put sizes 1-6 > size 6. If you decide to stick with your current suggested, don't use a hyphen between shoe size.

Also, if this crumb list matches categories in an ecom platform, make sure the categories have better page titles and <h1> than their category title suggests from this crumb list. For example, a category might show sizes 1-6 as its util title, and for crumbs and stuff...but when visiting that category, the page title and <h1> should be far more rich and descriptive. This is where you can get away with putting extra descriptor or long tail keywords in. Hope that makes sense :)

Vote Up Vote Down

@Deb1703797

A delimiter is simply a character (or more than 1) that separates content parts of data. For example:

> , / »


So, the right angle bracket > you used in your examples are considered delimiters.

The second one you suggest is redundant. It repeats the same keyword. There's no need.
Nothing to add about importance of user-centric approach in writing breadcrumbs.
But in this case, I think the one you consider "technical lingo" is in reality
the better for users.

If I have a parent category that says "Shoe sizes", I guess that the child of it would be a shoe size. In the case of a group of shoe size, I guess the grand-children would be a single size.

For further help in implementation, you should look at this thread that explains how to use structured data.

Breadcrumb using Schema.org rich snippets

Vote Up Vote Down