If you know something about SEO, you probably already know what WordPress Permalinks are and the huge impact they have on your website visibility around the web. For this very reason, changing their structure is not a trivial task and shouldn’t be underestimated by any webmaster or blog owner: not doing it properly will most likely result in broken links, 404 Page Not Found errors and other dreadful scenarios that will bring your SEO score down. In this post we will try to overcome these issues: however, before we do that, let’s make sure we’re all on the same track.
One of the most important things you can do to improve your website Search Engine Optimization (SEO) is to comply with the Unique page URLs rule, meaning that each page should answer to one – and only one – URL request. This rule covers even homepages, implying that you can’t have your website answer to multiple domain nams or alias (ryadel.com, www.ryadel.com, ryadel.net, www.ryadel.net, ryadel.org, www.ryadel.org): you have to pick and use your favorite one and properly configure a 301 redirect for all the others.
The redirect we need there is, as said, a standard HTTP 301 – permanent, which can be obtained in two ways: delegate the whole thing to your service provider, hoping he has an interface tool to allow you to configure it, or set their IP to your own server and handle the redirect using your web service (IIS, Apache et. al). If you don’t have direct access to your web server/web service interface manager you’re forced to take the first path, otherwise you can – and you should – choose the latter: you can do that in a matter of minutes as long as you’ll follow these rather simple instructions.
One of the most useful features of the WordPress platform is certainly the one allowing you to customize the Permalinks for each of our posts. As you might already know, the default settings of this feature can be set via the Settings > Permalinks tab in the Admin Panel: on top of that, each specific Permalink can also be reviewed and customized in the Edit Post page. Before going further, however, it may be useful to briefly summarize what these definitions actually mean. Read More
Since the first release of the .NET framework developers are given the chance to easily configure any kind of project – be it a Website, a Web Application, a Windows Forms or XPF/XAML client and such – in order to support multiple languages. This can be achieved using the well-known Resource Files (.resx) approach. We won’t explain them here (if you’re interested, read the official walkthrough), but we’ll remember a couple key concepts. A Resource Files is basically a key/value array of content resources (mostly images and text) for each supported language. All the developers have to do is to create a .resx file for the main language (let’s say english) and another one for each of these languages using the same name plus the ISO 639-1 two-letters language code of the language itself, i.e.:
- a Global.resx file to store text and images for english, assuming it’ll be our default & fallback language.
- a Global.it.resx file to store text and images for italian language
- a Global.de.resx file to store text and images for german language
and so on. Once we did that, we’ll only have to write our code using the key specified in these files instead of the actual content (if you don’t know how, read the walkthrough above): ASP.NET will look up the keys in our Resource Files, starting from the one with the Localization closest to the one set for the current thread and then going backwards until it founds something to show.
Kickass feature, indeed: let’s see how we can use it to build our very own multi-language MVC ASP.NET Web Application.
Favicon stands for Favorite Icon: we’re talking about the 16×16 px icon that identifies your website during the user navigation. Most browser shows it on the left side of the address bar, assuming the currently visited website has one. It’s also shown in the active navigation tab and in all of the browser’s favorites listings, menus and bars.
Why you should use it
It’s not merely aesthetics: favicon enables the user to identify the website he’s currently visiting, mentally group its pages/tabs in his browser window or inside his favorite list. A favicon-enabled website hooks up its users and simplifies their navigation, while also having a more professional look. That’s why, no matter what results you want to achieve on the web, you definitely want to have this kind of website.