NetNaps

Tag: Hosting

  • 20 Definitive Reasons for No Traffic On My Blog in 2020

    Here is a list of 20 Reasons for No Traffic on a Blog in 2020, I have written 20 Reasons you can please add more in the comments.

    Primary Reason: No New Visitors No New Traffic to the Blog

    This post is finding out reasons why blogs quit for no visitors

    If your blog doesn’t get organic traffic new visits even after many good efforts of creating content,
    that can frustrate a lot,

    you just keep on looking at the analytics, who visited your blog from which country what was the time spent on a particular post and so on.

    Well, Does that Make Sense?

    While as they say it all starts with a domain, an idea or a niche, it would never make sense to quit your blog,
    rather finding out reasons for no visitors is what your target should be if you follow your niche correctly just stick to what is required you won’t ever quit writing your blog.

    Finding reasons for No Traffic

    No traffic could be many valid reasons, here are some that I find relevant, you may add more in the comments below.

    Poor Design Worst User Experience Leading to No Traffic

    A poorly designed blog would never engage the visitors to read more, follow a blog or revisit it.

    Blogs that have lots of design elements, poor accessibility scores, for designs usually make the user quit the page and never return,

    It’s just same as visiting a new restaurant that has an ambience and food you are comfortable with and would repeat the visits.

    Always remember that first impression is the last!

    No Traffic for Not having a responsive layout

    This is one of the major reasons for lesser or no organic traffic, mobile-friendly pages that are responsive in all screen resolutions, cross-browser compatible, use technology like AMP for blogs are likely to get more impressions and rank higher.

    If you ignore how your website looks on a mobile screen most likely you will lose the traffic from search results.

    No Traffic as of Slow Pageload Speeds

    A visitor is most likely to leave your page. If the content loads slow, never loads or has errors, reasons can be many like not optimised images, poor hosting, weird server configuration, no use of CDN’s or in short no focus on the core web vitals.

    This performance now includes First Contentful Paint, Time to Interactive, Speed Index, Total Blocking Time, Largest Contentful Paint, Cumulative Layout Shift,  Critical Request Chains, Critical path latency, request counts and much more added frequently.

    Here is a list of many tools to check the performance of your website.

    Every page speed tool has its own term to determine the performance like Yslow considers DNS lookups as a performance score, while many other tools don’t consider this as a performance score.

    No Traffic as I am Giving away a damn to SEO

    SEO is not just getting the green lights on your WordPress Seo Plugin, It’s definitely beyond that or much more beyond that, The search engines are smarter than you can imagine, they change with the time improve with the technology stacks, your SEO plugin goes by the wish of the Developer how he wants it to be,

    I can see many plugins most popular one like Yoast has lots of open bugs, pending enhancements from years, ignoring then on its own with the one who suffers is the new blog who would require to match everything to outshine.

    Your blog won’t get organic traffic if you don’t follow how a search engine expects your content to be crawled, Things like Schema, Structured data play a vital role in the correct SEO strategy and plan.

    Posts that are in the Rich Snippets get the most clicks, more impressions. As soon as your posts hit the rich snippets for certain keywords, you would see a jump in your organic traffic.

    Greed to Monetize More More Ads Less Content So No Traffic

    With the greed to make money from a blog initially, placing more and more advertisements after each paragraph, on the fixed widgets on the footer, headers everywhere, adding affiliate links to almost all your lines you write, to monetise the blog whether or not its useful to the readers or visitors is another reason for no organic traffic.

    If you include more advertisements that eventually load more scripts, have more DNS lookups and more cookies making your page slow.

    Wasting time looking Income Reports of an old Successful Blog

    Most of the times new blogs get lured with the income charts, fake or real income disclosures, screenshots of an old blog site,

    Never understanding the real way they made success it wasn’t overnight, decades of work sticking to a single category, working contributing, building a community, helping in forums how pleasant the approach could be,

    only following the income of a blogger would not make you earn the same income even if if you follow them whatever they have done.

    I have seen some old blogs, and it has just become rather I would call it a weird trend to show off the income reports,

    but why only because they want to lure you with success stories, want you to follow them what they did to make money online, and then click on the affiliate links and make them more famous or richer?

    Content creation should be unique in your own way, not followed by how someone made a commission with affiliate programs or sponsored ads. So, Grow Up! Go to Work Create the Content.

    Please keep patience your time will don’t quit, keep on creating more and more good content.

    For the bloggers flaunting the income reports can let success make the noise please,

    Publishing Irrelevant Baseless Stuff for No Traffic

    I follow many blogs, even subscribe to the newsletters but why would I follow or subscribe?
    Only for some very good reasons like,

    Blogs that have helped me solve a problem, or have given me a reason to explore what’s new with them, as a visitor I would never return to a blog that has irrelevant and baseless stuff,

    With irrelevant I mean no relevance to the title and the post, like in this post I am writing about “Why the Blogs Quit”, So I should not write the tips what can be done along with each reason in detail.

    Yes, maybe a separate post would make sense.

    No Niche Topic, Blogging about Everything

    I have seen some Tech blogs discussing hosting. Also, writing about yoga, organic farming and writing about how to get admission to that Great University, to me as a visitor that looks like a piece of scrapped content nothing more than that, and I quit reading that blog.

    If you need to blog, you have to stick to your niche. Remember it’s your blog and not a country’s national newspaper.

    Backlinks From Everywhere

    When a new blog is built, you just thrive to get a backlink, irrespective of where the referral traffic comes from how authoritative the domain is, whats the class of the IP address it has?

    The link from a social media posting, again and again, spamming in social media groups, in comments to every other blog you visit just to make a backlink can also get you banned and your social media account can be suspended for spamming with posting links everywhere.

    The backlinks from social media sites, spam posts emails and forcing people to click with backlinks gradually makes a blog rank lower and with no organic traffic at all.

    No Traffic With Shared Hosting

    Hosting with a good host plays a vital role in getting organic traffic making your domain more authoritative, secure and available, get more and relevant pings and crawls from the search engines.

    A Class C Static IP address could also result in a better SEO,

    In short, when you get a Shared cheap hosting plan and start your blog, it’s mapped with many domains on the same IP address that could make your domain a culprit of another domain’s bad behaviour on the web.

    Longer Domain Names

    Usually, people don’t type or remember longer domain names. This can be a major reason for no traffic at all. Indexing is ok, but what if someone visited your blog and wants to reconcile with your post again to open it directly when he needs to refer the post again a shorter easy to remember name should preferably have good traffic.

    Selecting a wrong TLD

    When it comes to domain selection, and you see a list of available options if you select a wrong TLD for an example a most common TLD with .com is likely to get more traffic from all over the world than a TLD from a specific geo-location like .in for India .ca for Canada and so on.

    Geo-targeted TLD’s are often stuck to certain areas of the defined country that can be a major reason to get less traffic.

    Policy Violations No Indexing

    You might not even know, but you could have violated a policy of the search engine and they might have stopped indexing your site, could be another good reason for no traffic, regular check on guidelines best practices should be followed to avoid violations,

    You keep on creating the content but if your blog is not properly indexed would result in no organic traffic.

    No Security of the Visitor

    Search indexing will be better for a secure site on a secure hosting than a non-secured blog, I am not talking about getting the free SSL, security is beyond that the rating of your SSL the authority that has signed it, HSTS preloaded domain, How are cookies managed on your domain, If you allow users to signup how safe they are with signups. How you treat the privacy of the visitor?

    Everything for safety counts if you need traffic for your blog.

    Very Long Articles

    A blog with very very long articles, more than 2000 Words, are most likely to adversely affect the user engagement with the content, posts that do not stick to the title and the topic if you write irrelevant to what is not required for the topic or suddenly shift from the topic and start writing in between for another topic just to make the post contents long.

    The long blog post should be presented up in points, or with a table of contents at the top for users to jump to the relevant topics.

    Also its recommended to make short paragraphs that have a good readability.

    Lesser Posts Not Updating Content Frequently

    If you don’t post frequently have been or posting very fewer posts, that could be a reason that affects the visitors you receive.

    Visitors seek for blogs with new content every day if your blog is not updated; you are not likely to get organic traffic.

    If you created a HOW-TO a year ago and it has now changed completely, you should also update the same with updated steps, else that would become irrelevant for the visitor.
    Updating your posts and content is required regularly to maintain the user experience and get organic traffic.

    Switching over Hosting Zones and IP Addresses

    If you continuously shift over with hosting accounts, shift your sites entirely with where its available and hosted one zone to another zone and do not have a static availability can impact your traffic with my personal experience I shifted to Cloudflare for a day and suffered a loss of organic traffic for at least 14 days till everything became normal.

    The mistake I made was opting for a free plan to test something a few months ago. At the same time, I was saved by taking a quick decision to get back everything to normal AWS hosting, with using a static IP on my domain that has just my domain hosted and is not shared with any other domain name.

    Changing permalinks not monitoring your 404 Hits

    Mostly new blogs when start publishing keeps on changing permalinks and do not monitor the 404 hits, or maintain a 404 page, this could lead with slow indexing as when a visitor browses through the indexed URL, and he is directed to a blank 404 page it makes the worst user experience.

    Many of the blogs to improve change the permalinks make them shorter or change the entire structure of the URL. This can affect organic traffic, adversely resulting in less or no traffic.

    No Interaction with your blog users on comments

    When someone comments on your blog, and you do not reply to them at all, it sounds insulting, Quite similar to inviting someone to talk and not responding to them.



    Most likely the user won’t turn back again to your blog if you don’t respond, for the appreciation of your posts you should thank and reply like ” Glad my post was helpful”,

    For Answers, the author of the posts must be active to respond on the published content if the comment is not a relevant question you can direct them to something more relevant, you know.

    No promotion of your Blog

    If you have worked hard writing and making content, you should take out time to regularly promote your content the same with relevant posts to other authoritative blogs, like Quora, Medium and many more not doing so you will not get new traffic.

    You can also make a Facebook group of users to your blog, building a community to help will achieve regular readers for your blog.

  • Excellent Tricks For Redirection A Codes Collection

    Find below code snippets for Redirection, Change your domain name accordingly

    HTML Redirect / Javascript

    Simple Html + Javascript Redirect

    <!DOCTYPE HTML>
<html lang="en-US">
    <head>
        <meta charset="UTF-8">
        <meta http-equiv="refresh" content="0; url=https://netnaps.com">
        <script type="text/javascript">
            window.location.href = "https://netnaps.com"
        </script>
        <title>Redirect Me to Netnaps.com</title>
    </head>
    <body>
        <!-- Mention to Redirect, If Not Automatically -->
        If you are not redirected automatically, follow this <a href='https://netnaps.com'>link to NETNAPS</a>.
    </body>
</html>

    FallBack – Redirect if Javascript is not Allowed 

    <script>
    window.location.replace("https://netnaps.com");
</script>

<noscript>
    <a href="https://netnaps.com">Click here if you are not redirected automatically.</a>
</noscript>

    Redirection With Meta Tag in Delayed Seconds

    This is 5 seconds Delayed delay as you like

    <meta http-equiv="refresh" content="5; url=https://netnaps.com/" />

    INIT Function With HTML Redirection

    <!DOCTYPE html>
<html>
    <head>
        <title>Example</title>
        <script>
            function init()
            {
               window.location.href = "www.netnaps.com";
            }
        </script>
    </head>

    <body onload="init()">
    </body>
</html>

    Apache Server .htaccess Redirections

    Permanent Redirect 301 Non-www to www

    #redirect non-www to www
RewriteEngine On
RewriteCond %{HTTP_HOST} !^www\.
RewriteRule ^(.*)$ https://www.%{HTTP_HOST}/$1 [R=301,L]

    Redirecting permanently www to non-www domain

    RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ https://%1/$1 [R=301,L]

    Redirecting a www domain with folder or sub-directory permanent 301

    RewriteEngine on
RewriteBase /
RewriteCond %{HTTP_HOST} netnaps.com [NC]
RewriteRule ^(.*)$ https://netnaps.com/directory/index.html [R=301,NC

    Redirect an old domain to the new one with a full query string and path

    Options +FollowSymLinks
RewriteEngine On
RewriteRule ^(.*) https://netnaps.com%{REQUEST_URI} [R=302,NC

    Redirect The Entire Web Site 

    Redirect 301 / https://netnaps.com/

    Redirecting a particular page 

    Redirect 301 /index.php https://netnaps.com/blog

    Redirect the Site to a Folder / Directory

    Redirect 301 / http://www.domain.com/subfolder/

    HTML to PHP File Redirection 

    RedirectMatch 301 (.*)\.html$ https://netnaps.com$1.php

    Redirecting an Old Domain to A New Domain

    RewriteEngine on
RewriteBase /
RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

    Nginx Redirects

    Nginx All HTTP Requests to HTTPS

    Use anyone both worked for me, If you use 443 Port use First One

    server {
  listen [::]:80;
  listen      80;
  server_name netnaps.com www.netnaps.com;

  # Redirect all non-https requests
  rewrite ^ https://$host$request_uri? permanent;
}
    

server {
  listen              80;
  listen              [::]:80;
  server_name         netnaps.com www.netnaps.com;
  location '/var/www/netnaps' {
  default_type "text/plain";
  root        /tmp/dir;
  }

  location / {
    return              301 https://$server_name$request_uri;
  }
}

    PHP Redirects 

    <?php
    Header("HTTP/1.1 301 Moved Permanently");
    Header("Location: https://netnaps.com");
?>

  • Lightsail SFTP Access With FileZilla Easily 5 Steps

    Saturday 8 August 01:09

    Getting Lightsail SFTP Access is Quite Easy

    Required Supply: Lightsail Account, Tools Needed: Filezilla

    In these short 5 Steps, we will learn How to get Lightsail SFTP Access or Connect Lightsail Instance to Filezilla using SFTP.

    To get access to the hosted file directory on the server.

    Also, find a command for setting up permissions to use at the end of this short tutorial.

    Lightsail SFTP Access Using FileZilla
    You can log in with your account on the Lightsail page :
    https://aws.amazon.com/lightsail/ Lightsail SFTP Access Using FileZilla.

    Step Click on your Instance

    click on lightsail
    Just click on your instance, to get started once you click it will show Connect Using SSH button

    Step 2 Scroll down and go to Account Page link

    account page lightsail
    Here you will find Keys of all the zones to connect via FTP

    Step 3 Download your Key File

    Download your key file
    This key is required to log in, keep this in a safe place after download.

    Step 4 Open FileZilla to Add a New Site

    open filezilla app
    Click on the extreme left top corner to add a new site.

    Step 5 Add the Details of New Site


    As we have explained in our screenshot, click on New Site ( No.1 Arrow ) Name Your Site,
    Select SFTP in the first option, and add your Lightsail Instance static IP / or public IP address.

    In Logon Type select key file, and the user is bitnami as you see in your SSH Terminal window, Add Key file location like normally you select a file.

    Then Connect, and it’s Done!

    Lightsail SFTP Access Bonus Tip – To Set Up Permissions.

    sudo chown -R bitnami:bitnami /opt/bitnami/apps/wordpress/htdocs/wp-content/

    This target folder could be anything wp-content is just for an example. If you need both users to have permissions, you can use bitnami: daemon and likewise.

    Without proper permission, you will not be able to upload any new file or make changes to your directory. You can still view the files.

    As in this above tutorial, we have signed in as bitnami, so the user is bitnami.

    Before you start your WordPress with any paid hosting, you can make it for free on your Mac, With this detailed tutorial here. Also, you can make this as a testing or development environment on your local mac.

    The tutorial for WordPress on a mac is free and also lets you get a free SSL if you wish to start an AMP Website or a Blog.

    I, too, am using Lightsail as a hosting and AMP on this blog! Powered by WordPress

  • Backup Lightsail instance with free SnapShots in 3 Steps

    Amazon Lightsail is a popular cloud platform that offers simple virtual private servers (VPS) for developers, small businesses, and hobbyists. While Lightsail makes it easy to deploy and manage servers, backing up your instance is crucial to protect your data and ensure business continuity. Fortunately, Lightsail provides a free and straightforward way to create backups using Snapshots. In this article, we’ll walk you through how to back up your Lightsail instance in just 3 simple steps.

    Why Backup Your Lightsail Instance?

    Before diving into the steps, let’s understand why backups are essential:

    1. Data Protection: Accidental deletions, corruption, or hardware failures can lead to data loss.
    2. Disaster Recovery: In case of a server crash or cyberattack, backups ensure you can restore your system quickly.
    3. Cost-Effective: Lightsail offers free snapshots for the first snapshot per instance, making it an affordable solution.

    Now, let’s get started!

    Step 1: Log in to Your AWS Lightsail Console

    1. Go to the AWS Lightsail Console.
    2. Log in with your AWS credentials. If you don’t have an AWS account, you’ll need to create one.
    3. Once logged in, you’ll see a list of your Lightsail instances. Select the instance you want to back up.

    Step 2: Create a Snapshot of Your Instance

    1. Navigate to the Snapshots Tab:
    • In the Lightsail dashboard, click on the instance you want to back up.
    • Go to the Snapshots tab in the instance management section.
    1. Create a Snapshot:
    • Click the Create Snapshot button.
    • Give your snapshot a meaningful name (e.g., MyInstance-Backup-Oct2023).
    • Click Create to start the snapshot process.
    1. Wait for the Snapshot to Complete:
    • The snapshot creation process may take a few minutes, depending on the size of your instance.
    • You can monitor the progress in the Snapshots tab.

    Step 3: Restore or Manage Your Snapshots

    Once your snapshot is created, you can use it to restore your instance or create a new instance from the backup. Here’s how:

    1. Restore an Instance:
    • Go to the Snapshots tab.
    • Select the snapshot you want to restore.
    • Click Create New Instance to spin up a new instance from the snapshot.
    1. Delete Old Snapshots:
    • If you no longer need a snapshot, you can delete it to free up space.
    • Go to the Snapshots tab, select the snapshot, and click Delete.
    1. Automate Snapshots (Optional):
    • Lightsail allows you to enable automatic snapshots for daily backups.
    • Go to the Snapshots tab and toggle the Enable Automatic Snapshots option.

    Benefits of Using Lightsail Snapshots

    • Free for the First Snapshot: Lightsail offers the first snapshot per instance for free, making it a cost-effective backup solution.
    • Easy to Use: The process is simple and doesn’t require technical expertise.
    • Quick Recovery: Snapshots allow you to restore your instance in minutes, minimizing downtime.

    Tips for Effective Backup Management

    1. Regular Backups: Create snapshots regularly to ensure your data is always protected.
    2. Name Your Snapshots: Use descriptive names to easily identify backups.
    3. Enable Automatic Snapshots: Automate the process to avoid forgetting manual backups.
    4. Test Your Backups: Periodically restore a snapshot to ensure it works as expected.

    Conclusion

    Backing up your Lightsail instance with snapshots is a simple yet powerful way to safeguard your data and ensure business continuity. With just 3 easy steps—logging in, creating a snapshot, and managing your backups—you can protect your server from data loss and disasters. Plus, with the first snapshot being free, there’s no reason not to get started today!

    Have you tried using Lightsail snapshots? Share your experience or any tips in the comments below!