Google indexes the content inside an iframe

Perhaps you already know if Google does not index the content inside an iframe, so the comments from Disqus or Facebook is not indexed.

But now Google has started indexing the content inside an iframe, I realized this today when I checked the HTMLy blog demo, Danlogs.

The blogs using Disqus comments, and it turns out all the comments on the blog indexed by Google. A certainly good news for Disqus users.

For Facebook comments, I have not yet figured out its already indexed or not, but it should also being indexed because it uses an iframe as well.

HTMLy: Databaseless Blogging Platform (Flat CMS)

There are times when we just want to write without having to think about site management, for example upgrading to the latest version (core and plugin), for this purpose I developed a blogging platform that does not use a database at all, so just write and write.

Although prioritizing simplicity and speed, but the platform also includes standard features available on a blog in general, for example:

  • Admin panel
  • Markdown editor with live preview
  • Categorization with tags (multi tags support)
  • Static pages Eg. for contact page
  • Meta canonical, description, and rich snippets for SEO
  • Pagination
  • Author page
  • Multi author support
  • Social links
  • Disqus Comments (optional)
  • Facebook Comments (optional)
  • Google Analytics
  • Built-in search
  • Related posts
  • Per post navigation (previous and next post)
  • Body class for easy theming
  • Breadcrumb
  • Archive page (by year, year-month, or year-month-day)
  • JSON API
  • OPML
  • RSS Feed
  • RSS 2.0 Importer (basic)
  • Sitemap.xml
  • Archive and tag cloud widget
  • SEO friendly URLs
  • Teaser thumbnail for images and Youtube videos
  • Responsive design
  • Lightbox
  • User role
  • Online backup

This platform is a kind of static web page (Flat CMS) in general but using markdown file to store all its posts. Creation date, category, and the URL is taken from the name of the file, example:

2013-12-25-12-56-40_general_url-of-the-post.md

Here's the explanation (separated by an underscore):

  • 2013-12-25-12-56-40 is the published date
  • general is the tag/category
  • url-of-the-post.md is forming the main url

So we only need to give the name of the file with above format and then upload them to a specified folder, in this case is inside content/author/blog folder for the blog post and content/static for static page.

For static pages I use the following format:

about.md

This means that about as the URL.

Why use a file name?

We believe if the performance will be faster by read the file name, filters it, then read the file content that are matched. Although this may change in the future.

What is the minimum requirements?

HTMLy only require PHP 5.3+, yes no database needed to run HTMLy.

So how do I get it?

You can download it on GitHub. Visit a real blog powered by HTMLy on Danlogs, or visit the official homepage at HTMLy.

Updating Discourse on CentOS

I have one forum using Discourse, as a test for this new platform, for OS I use CentOS. Discourse official documentation to updating the site is using Ubuntu so there are a few changes need to be done for CentOS.

My SSH login name is Discourse and the installation folder is inside the Discourse folder, example url

/home/discourse/discourse

Here's how to update Discourse to the latest version:

# Run these commands as the discourse user
bluepill stop
bluepill quit

# Back up your install
DATESTAMP=$(TZ=UTC date +%F-%T)

pg_dump --no-owner --clean discourse_prod | gzip -c > ~/discourse-db-$DATESTAMP.sql.gz

tar cfz ~/discourse-dir-$DATESTAMP.tar.gz -C /home/discourse discourse

# Get the latest Discourse code
cd discourse
git checkout master
git pull
git fetch --tags

# To run on the latest numbered release instead of bleeding-edge:
# git checkout latest-release

# Merge the sample configuration just in case if there is an update. Run these commands as the discourse user

diff -u config/discourse_defaults.conf config/discourse.conf

diff -u config/discourse.pill.sample config/discourse.pill

diff -u config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf

# Begin upgrade
bundle install --without test --deployment

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake assets:precompile

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ROOT=/home/discourse/discourse RAILS_ENV=production NUM_WEBS=2 bluepill --no-privileged -c ~/.bluepill load /home/discourse/discourse/config/discourse.pill

# Restart bluepill
crontab -l

Google Penguin 2.1 is active

Google has released an update to the Google Penguin algorithm , the Penguin version 2.1. Matt Cutts himself who announced via Twitter, the following is Matt's tweet:

I do not see a significant effect with the 2.1 release of Google Penguin in all of my website/blog.

Now Adsense support HTTPS site

After a long-awaited, Adsense now supports HTTPS sites, the following is the official announcement from Google Adsense blog:

Inside AdSense: Use AdSense on your HTTPS sites: Today, we're happy to announce that AdSense publishers can begin monetizing their HTTPS pages. Many websites, like e-commerce sites and social networking sites, use the HTTPS protocol to protect their users' sensitive data. If you have a HTTPS website you’ll be pleased with how easy it is to monetize using AdSense.

Good news if your site is using HTTPS protocol.