1. Login to your self-hosted WordPress blog -> Appearance -> Editor

2. Click Single.php and find this code:

<a href="<?php the_permalink() ?>" rel="bookmark" title="Permanent Link to <?php the_title_attribute(); ?>"><?php the_title(); ?></a>

3. Delete and replace it with this code:
<?php the_title(); ?>

4. Click Update File. Done.

Both urls directing toward the same post or page which means you have duplicate contents according to Google eyes. You may know this problem by logging into your Google Webmaster Tools.

If you got that kind of dupicate contents after installing W3 Total Cache plugins, the most probable cause is the plugins itself. Here’s how to fix the problem:

1. Login to your self-hosted wordpress blog. Locate the W3 Total Cache admin
2. Click Performance -> General Settings -> Page Cache -> opt for Disc (Basic) NOT Disc (enhanced).
3. Save updates. Done.

Further reading

I don’t have the choice to return back to Super-cache plugins, because my webhosting provider asked me to do so.

After some search I got these solutions to resolve the issue none of which are working for me.

After login to your self-hosted blog, click W3 Total Cache -> Performance -> General Settings and try the following settings one by one:

1. Disable feed cache in Page  Cache -> Cache Feeds -> uncheck

2. Disable Minify. General settings -> Minify -> uncheck.

Reducting Feed Size

Another way to solve the problem is by reducing the feed size below 512 k as permitted by Feedburner.

To reduce feed size, just go login to your self-hosted wordpress blog -> Settings -> Readings -> change into the lower number. Example 3 -> Save update.

Among many causes that I have experienced frequently is a bad post.

1.Bad Post
2. Cause
3. Solution
4. Consequences of Feed Error
5. How to Know
6. Feedburner Error and Solution

1. Common Problems
2. Resync

1. What’s a bad post?

A bad post is not a bad writing or low quality article / post.
Google explains[1] that a post is considered bad and will cause feed error if:

Your feed has these XML tags in it:

Code:

<o:p>(some text)</o:p>

It is very likely that your feed will be considered invalid by FeedBurner, Feed Validator, and possibly many other places to which you want your feed properly distributed. The result is that FeedBurner will stop updating its version of your feed until the validation problem is repaired.

2. The Cause:
The <o:p> tag is usually introduced by a copy-paste of original text from Microsoft Word or another Office application; this tag originates in a Microsoft XML “namespace,” or definition of a custom set of tags used for XML markup.

In general, using word processing applications to compose blog posts can lead to unexpected results (such as this one).

3. The Solution:
1. The best way to avoid this problem is to avoid composing and copying content from Word into your blogging tools.

2. If you still want to use content found in Office applications, a common trick for removing extraneous code is to “clean” copied text by pasting it into a plain text editor, such as Notepad (Windows) or TextEdit (Mac) and the copying the newly cleaned text before pasting it into your blogging application.

3. Compose new posts in a text editor recommended or provided by your blog platform publisher only.

4. Consequenses

The consequences of a feed error caused by bad post or others are many. Among which being (a) your post or articles will not be distributed, (2) if you integrate your feed with Feedburner and join Adsense for Feed, the Adsense will not show up in the feed. Thus missing potential revenue.

5. How to Know

1. Check regularly your feed’s health through feedvalidator.org
2. If you join Feedburner, check also your Feedburner feed.

6. Feedburner Error and Solution
If you integrate your blog feed into Feedburner, you may look into the following issues and how to fix them [2]

The most common problems that affect your FeedBurner feed are:

1. The trouble: Your FeedBurner feed isn’t up-to-date with your Original Feed.

The fix: Try pinging FeedBurner using our Ping page. This action tells FeedBurner to go check your feed for updates immediately.

2. The trouble: Invalid characters or XML markup in content items, often introduced by composing your posts in Microsoft Word or embedding JavaScript code in a post.

The fix: Check your feeds for validity problems: Original Feed Validity, FeedBurner Feed Validity. See if any errors are reported, Then, check out this help topic for removing unwanted characters from your posts if mysterious characters seem to be to blame.

3. The trouble: Connection timeouts between FeedBurner and the web server that hosts your original feed. If FeedBurner can’t reach your Original Feed for any reason, we will report it as a FeedMedic item here on Troubleshootize.

The fix: Try a ping once your website service has been restored.

4. The trouble: For podcasters, the web server hosting your audio does not report the correct content MIME type for your podcast files; FeedBurner doesn’t create podcast enclosures for these files.

The fix: Make sure your web server is configured to return “audio/mpeg” as a MIME type for your audio files (or whatever the appropriate type for your podcast media may be). This confirmation may require some help from your hosting provider if you do not manage your own web server.

5. The trouble: Your Original Feed is too doggone big! FeedBurner does not process feeds that are larger than 512K. Remember, your feed is an update on your content — not an archive for it — and you should use your publishing tools’ controls to make sure your feed doesn’t grow like kudzu possessed.

The fix: Follow this help topic to control feed file size with Blogger; other publishing tools have similar controls.

The last solution: RESYNC

Resync takes the following actions:

1. Clears our cached version and refreshes its content from your Original Feed
2. Creates podcast enclosures for items that did not previously have them and contain links to podcast content
3. Reports any feed formatting problems encountered during the resync

When to use Resync:

1. As a last resort with a regular feed or a podcast, you can resync your feed.
2. You should only resync if (a) your feed is more than 1 hour out-of-date and (b) pinging FeedBurner does not update it or (c) your podcast files are not being turned into enclosures by our SmartCast service.

How to Resync Feedburner

1. Login to your Feedburner account
2. Click your Blog feed in trouble
3. Click Trobleshootize
4. Click Resync at the bottom. Done.

=====
Note:
[1] Google Support
[2] Feedburner troubleshooting

If you are an Arabic native speaker where you’re more comfortable with Arabic letters and everythng Arab, you’re advised to use WordPress in Arabic which can be downloaded from www.ar-wp.com.

Discussion forum in for WordPress Arabic users are also available in the site.

But if you’re more comfortable with WordPress dashboard in English or Bahasa Indonesia at the same time you would also enable Arabic fonts/letters in posts, pages and comments, you may follow this tutorial below:

1. Login to you Cpanel (yoursite.com/cpanel), find menu PHPMyAdmin.
2. Find the database of your blog. Select the table “wp_posts“, edit the field of “post_content“.
3. Change the collation in to “utf8_general_ci”
4. Save. You’re done.

1. Google XML Sitemaps
2. Dagon Design Sitemap Generator
3. XML Sitemaps
4. Really Simple Sitemap
5. Google Sitemaps Append UTW Tags
6. Karailiev’s Sitemap
7. WP Realtime Sitemap
8. WP Shopping Cart XML Sitemap
9. Google XML Sitemap for Videos
10. Googe News Sitemap

Here’s Robots.txt file example which is good for SEO (search engine optimization) according to WP

User-agent: *
Disallow: /cgi-bin
Disallow: /wp-admin
Disallow: /wp-includes
Disallow: /wp-content/plugins
Disallow: /wp-content/cache
Disallow: /wp-content/themes
Disallow: /trackback
Disallow: /feed
Disallow: /comments
Disallow: /category/*/*
Disallow: */trackback
Disallow: */feed
Disallow: */comments
Disallow: /*?*
Disallow: /*?
Allow: /wp-content/uploads

# Google Image
User-agent: Googlebot-Image
Disallow:
Allow: /*

# Google AdSense
User-agent: Mediapartners-Google*
Disallow:
Allow: /*

# digg mirror
User-agent: duggmirror
Disallow: /

Sitemap: http://www.example.com/sitemap.xml

Don’t know how to create robots.txt file? See here.

Another sample of a good robots.txt file is here.

Search spiders and other computer programs (grouped together as “bots”) go through your web pages by scanning the source code – What you see if you right-click on a web page and select “View Source”.

You may create a robot.txt file in a notepad as follow:

1. Click Notepad from your computer
2. Write the following:
User-agent: *
Disallow:
3. Save it.
4. Upload it to the root directory. For example, if you blog is website.com, the file should be uploaded in public_html/–upload here–
5. Done.

Another format of robot.txt is as follow:

User-agent: *
Allow: /

Note: You cannot create Robot.txt file in a Blogspot or WordPress.com blog as you don’t have access to the root level directory. It can be done in a self-hosted blog only.

If you check your website through Google Webmaster Tools, you’ll find there are some URLs which are ended in unwanted variables / characters such as http://www.fatihsyuhud.com/seo/EygMYqwqH instead of http://www.fatihsyuhud.com/seo/

In such case, what you have to do is to install Permalink Redirect plugin by Yoast, activate it. That’s it. From now on anyone who come to the URL http://www.fatihsyuhud.com/seo/EygMYqwqH would be redirected to the true URL that is http://www.fatihsyuhud.com/seo/

If you’re interested, you may download it here for free.