SEO Blues – Keyword Rich URL Conflicts Menu in Weebly
November 22, 2011 Tags: keywords, menu, navigation, seo tips
Category: Menus & Navigation, SEO 2 Comments 
In SEO Tip 15, we discuss the benefit of using a keyword rich url for better search engine ranking. This is the most critical requirement with raking high for targeted keywords.
But with Weebly, the url and page name have to be the same. A keyword rich url would make the page name longer. This would all be fine for hidden pages. However, if you need the page to show up in Menu navigation, you are going to have a lengthy menu bar navigation item which compromises the look and feel of Menu.
Here is how you can get the best of the both worlds. First, create pages with keyword rich urls so that they can rank well. Then mark these pages hidden. Now, inorder to create short Menu Navigation item for these hidden pages, create pages as links to external pages. In the place of external link, use the link of your hidden keyword rich page url. That should solve the problem of having shorter menu item and at the same time keeping a keyword rich url.
It would have been ideal if there were an option to create a navigation label different from page name. Since that is not available with Weebly, you need to use this workaround to enhance usability and navigation without compromising Search Engine Raking.
Hi, what impacts do fonts have on SEO ? In Yola you can pick heading 1,2,3 etc and normal paragraph for text. Do the H1 get picked up better than H2, H2 better than H3 etc…
You brought up a very important aspect of SEO. H1 has higher priority than H2. H2 has higher priority than H3. People argue that H4, H5, H6 are placed at one level below H3. But they are all above regular paragraph text. But making the entire text a heading would nullify the priority altogether.
Yola gives custom control on headings which is very good for SEO. Weebly sets site title at H1. For Title in elements Title-with-text and Title only, Weebly sets a H2 priority. That is the only control available unless one intends to use custom-html element to set the rest of the tags.