#[ERROR 404 FILE NOT FOUND- Crack] | Explore Tumblr posts and blogs

ms-demeanor · 3 years ago

Text

Okay so you know how I'm constitutionally incapable of letting things go?

I'm still on about the Jake Parker Alphonso Dunn thing and I finally cracked and created a pacer account and downloaded the initial filing of the lawsuit. Here's my favorite quote from it:

"Pen and ink drawing, however, is not as inviting a drawing medium as pencil, especially for beginners or anyone new to drawing, for several reasons [...] This explains why there is a drastically limited number of comprehensive ink drawing instruction books and learning resources available today as compared to the hundreds, if not thousands, of pencil drawing books.

Upon information and belief, there are less than 10 widely known comprehensive ink drawing instruction books in the art community."

Every single link in that quote is a link to a comprehensive ink drawing book that is/was widely available. Even if you don't count the ones that are out of print (but are in libraries, art classrooms, and are available online) you're still looking at *at least* ten, one of which has been in continuous publication for 100 years and two of which are different books written by one author. Also I own two books that aren't even directly linked here (both about cartooning) that include comprehensive pen and ink techniques as part of a larger whole and cover materials materially similar to what Dunn is saying was plagiarized, and that's not even getting into the really specific and narrow "pen and ink animals" "drawing in ballpoint pen" "pen and ink landscape" "pen and ink for comics" "pen and ink and watercolor" "pen and ink and charcoal" books that are out there that also cover basic pen and ink technique in a pretty comprehensive way. There are so many pen and ink instruction books that attempting to open links to all of them in the various places that I found them crashed my browser.

He also really, really doubles down on "there is no functional difference between these sections and the layouts are identical" when A) there is a functional difference because Dunn wrote a technical instruction guide and Parker wrote a low-key how-to book for casuals that is primarily about motivation and mindset and B) Dunn's book has a strong vertical layout and Parker's is square.

It is making me bugfuck crazy that he's claiming these two layouts are duplicates.

One of these pages is twice as tall as the other. One has a centered brushstroke font as the header with descriptions under each of four tools; One has left-aligned text with a sans serif header and single-word descriptions next to nine tools. One has tools that are presented illustrated at an angle that points to the gutter of the layout, one has tools that point to the center of the page. We are, literally, not the same.

My second favorite quote from the lawsuit is this:

"Dunn has found many supporters online, who believe that Parker has committed plagiarism and infringed on Dunn's copyrighted works."

Friend, what your twitter followers think isn't legally actionable.

The suit claims that the uses of Dunn's work were numerous and far reaching, but looking at the images used in the filing it kind of looks like Dunn hasn't gotten a copy of the book and is still screencapping from the ten images on Amazon. Shoutout to this absolute maniac on Pinterest who not only did a side-by-side comparison of Inktober All Year and Pen & Ink Drawing but also compared Pen & Ink Drawing to a bunch of other ink illustration books. Also I'm pretty sure Inktober All Year Long is unreleased and the lawsuit is based on sales continuing until December 2020 but I can't find the book anywhere new or used and the few people who have reviewed it have claimed they got it because Amazon sent it to them on accident after delivery was cancelled and every seller that I can find that had links to it lists it as backordered or now has a 404 error for the book.

Here's another pertinent quote from the suit:

Authors instruct on pen and ink drawings in multiple ways. Dunn's work, however, is not the result of restating standard methods or formulae, but is his original expression born from his creativity.

I do continue to feel really, really bad for Alphonso Dunn, because it really seems like he spent a lot of time reinventing the wheel and is upset that a similarly popular artist is also making a wheel. Like, in the original video he REALLY fixates on the idea of "varying" strokes, and insists that the use of the word "varied" or "variable" must be plagiarized from him because he spent so long coming up with the right word to use for that technique - but the 100-year-old pen and ink instruction book I discussed earlier has a multi-page layout about varied strokes.

Anyway the lawsuit was filed in September of 2021 and so far it's been just a shitload of extensions to serve papers and motions to dismiss and motions to extend the time to respond to the motion to dismiss.

I don't think that Parker is perfect (I actually find him pretty annoying and I do agree that it is very questionable to claim exclusive ownership of an event that became popular because of millions of participants) and I don't think that Dunn is malicious, but in this case I do think that Dunn is wrong. This guy has a take on it that pretty much aligns with my opinion.

And I'm interested in the outcome of the case because a lot of the claims that Dunn made in his video and appears to reiterate in the case have to do with attempting to claim exclusive rights to teach art fundamentals using extant language, so that's actually pretty important!

Anyway I am going to continue to Be Weird about it.

252 notes · View notes

pandamains · 3 years ago

Text

Steel beasts gold no cd crack

Steel beasts gold no cd crack how to#

Steel beasts gold no cd crack code#

Test your website to make sure your changes were successfully saved.Click Save Changes in the upper right hand corner when done.A dialogue box may appear asking you about encoding.

Steel beasts gold no cd crack code#

htaccess file and then click on the Code Editor icon at the top of the page. Alternatively, you can click on the icon for the. htaccess file and click Code Edit from the menu. The File Manager will open in a new tab or window.

Make sure Show Hidden Files (dotfiles)" is checked.

Check the box for Document Root for and select the domain name you wish to access from the drop-down menu.

In the Files section, click on the File Manager icon.

htaccess files in cPanel's File Managerīefore you do anything, it is suggested that you backup your website so that you can revert back to a previous version if something goes wrong. htaccess file for most people is through the File Manager in cPanel.

Edit the file on your computer and upload it to the server via FTP.

Steel beasts gold no cd crack how to#

htaccess file at some point, for various reasons.This section covers how to edit the file in cPanel, but not what may need to be changed.(You may need to consult other articles and resources for that information.) There are Many Ways to Edit a. It is possible that you may need to edit the. htaccess file, and many scripts such as WordPress, Drupal, Joomla and Magento add directives to the. Redirects and rewriting URLs are two very common directives found in a. htaccess file contains directives (instructions) that tell the server how to behave in certain scenarios and directly affect how your website functions. On platforms that enforce case-sensitivity PNG and png are not the same locations. Notice that the CaSe is important in this example. In this example the image file must be in public_html/cgi-sys/images/ This varies by browser, if you do not see a box on your page with a red X try right clicking on the page, then select View Page Info, and goto the Media Tab. The properties will tell you the path and file name that cannot be found. Right click on the X and choose Properties. When you have a missing image on your site you may see a box on your page with with a red X where the image is missing. On platforms that enforce case-sensitivity example and Example are not the same locations.įor addon domains, the file must be in public_html//example/Example/ and the names are case-sensitive. In this example the file must be in public_html/example/Example/ When you get a 404 error be sure to check the URL that you are attempting to use in your browser.This tells the server what resource it should attempt to request.

#Steel beasts gold no cd crack

1 note · View note

tamphong2888 · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

The only tool that can give you a real overview of how search engines crawl your site are log files. Despite this, many people are still obsessed with crawl budget — the number of URLs Googlebot can and wants to crawl.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

While it’s a fascinating topic, the fact is that most sites don’t need to worry that much about crawl budget —an observation shared by John Mueller (Webmaster Trends Analyst at Google) quite a few times already.

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

When you know exactly what your log files are telling you, you’ll gain valuable insights about how Google crawls and views your site, which means you can optimize for this data to increase traffic. And the bigger the site, the greater the impact fixing these issues will have.

What are server logs?

A log file is a recording of everything that goes in and out of a server. Think of it as a ledger of requests made by crawlers and real users. You can see exactly what resources Google is crawling on your site.

You can also see what errors need your attention. For instance, one of the issues we uncovered with our analysis was that our CMS created two URLs for each page and Google discovered both. This led to duplicate content issues because two URLs with the same content was competing against each other.

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/eSXNch) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

There are many tools you can choose from that will help you analyze your log files. I won’t give you a full run-down of available ones, but it’s important to know the difference between static and real-time tools.

Static — This only analyzes a static file. You can’t extend the time frame. Want to analyze another period? You need to request a new log file. My favourite tool for analyzing static log files is Power BI.

Real-time — Gives you direct access to logs. I really like open source ELK Stack (Elasticsearch, Logstash, and Kibana). It takes a moderate effort to implement it but once the stack is ready, it allows me changing the time frame based on my needs without needing to contact our developers.

Start analyzing

Don’t just dive into logs with a hope to find something — start asking questions. If you don’t formulate your questions at the beginning, you will end up in a rabbit hole with no direction and no real insights.

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

Order the list by the number of requests, evaluate the ones with the highest number to find the pages with the highest priority (the more requests, the higher priority), and consider whether to redirect that URL or do any other action.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

Grouping data into segments provides aggregate numbers that give you the big picture. This makes it easier to spot trends you might have missed by looking only at individual URLs. You can locate problematic sections and drill down if needed.

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

Your site changes over time, which means so will crawlers’ behavior. Googlebot often decreases or increases the crawl rate based on factors such as a page’s speed, internal link structure, and the existence of crawl traps.

It’s a good idea to check in with your log files throughout the year or when executing website changes. I look at logs almost on a weekly basis when releasing significant changes for large websites.

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

While it’s no necessary to connect to other data sources, doing so will unlock another level of insight and context that regular log analysis might not be able to give you. An ability to easily connect multiple datasets and extract insights from them is the main reason why Power BI is my tool of choice, but you can use any tool that you’re familiar with (e.g. Tableau).

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You may be surprised by the insights you’ll uncover that can help strengthen your SEO strategy. For instance, discovering that almost 70 percent of Googlebot requests are for pages that are not indexable is an insight you can act on.

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Last year, Google Analytics reported a drop in organic traffic for our branded search queries. But our keyword tracking tool, STAT Search Analytics, and other tools showed no movement that would have warranted the drop. So, what was going on?

Server logs helped us understand the situation: There was no real drop in traffic. It was our newly deployed WAF (Web Application Firewall) that was overriding the referrer, which caused some organic traffic to be incorrectly classified as direct traffic in Google Analytics.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

My advice is to start with segmenting data and monitoring changes over time. Once you feel ready, explore the possibilities of blending logs with your crawl data or Google Analytics. That’s where great insights are hidden.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don't have time to hunt down but want to read!

1 note · View note

we-in-the-aftermath · 8 years ago

Text

RANDOM FACTS ABOUT THE MUN.

Repost, not reblog! Tag 6 muns you would like to get to know better when done!

Whoops, this got a bit long!

Name: [[Error 404 File not Found]] Nickname: Raine Age: 14 (Narsh is a lil kiddie) Faceclaim: it was Iris.exe, but she has like no expressions. Sooooo…. Rockman.exe it is! Pronouns: she/her Height: 5'4" Birthday: February 1st! Aesthetic: Cool-colored (green blue purple) crystals, rain(…e. HA), and retro game systems & cartridges Last song you listened to: …….my memory is crap but I think like Katrina’s Theme from Romancing SaGa 3, played on piano by my dad. I’ve had Remember When (remixed by NightcoreReality) stuck in my head all day though.

Favorite muse(s) you’ve written: Are we talking favorite backstory or favorite to write or what. The short answer is that it really changes depending on my mood. I’m a very impulsive RPer, so most of my responses come from the heart and that’s a very fickle thing. I love Pandora but she’s very hard to write threads for given that she’s a villain. Proto is great but he’s so suspicious of strangers that he’s not at peak interaction for most threads. I love X and O, but they’re Biometals and that’s hard to work into a thread. Forte would probably make for boring threads, Serenade has a job, and Chronos is a villain that I don’t have entirely figured out yet. Probably X is my favorite since he’s like a better version of me, but I also really want to write Pandora because she’s just Really Great.

What inspired you to take on your current muse (that your are posting this on): Okay Narsh kinda touched on this but I’m going to go way more in-depth because this is important to me. Basically, sometime in early August 2015, Narsh and I were texting. I had been reading some things on DeviantArt where in the comments some people would write a comment and then write the character’s reaction to it. I soak up other writing styles really easily and it leaked into our text thread. I called Proto “Bluesy-kun~” and he got annoyed at that. Then Narsh, who had been playing Mega Man ZX (and that was the only MM universe she really knew), responded with Model Z teasing Proto. So it all started with just absolute random silliness. And then a week later or so we started our habit of writing serious/angst interactions and then Aile adopted Proto. Whoops. The other universes that got roped in were entirely my fault. I was falling deep into obsession with everything Mega Man, and branching out to the other versions (being introduced to each by reading tons of fanfiction, including about things I didn’t know about. I’m the type of person who is glad to be dropped into the middle of something and figure it out through logic). For instance, I started watching the Mega Man NT Warrior anime and thought Forte.exe was the coolest character ever. So I put him in. It’s lasted this long and been fleshed out quite a bit with… almost three years under its belt? Wow. TL;DR - Narsh and Fanfiction.

What are your favorite aspects of your current muse: The family dynamics between Pandora/Prometheus, Proto/Robot Masters, Proto/Blues/Break, Proto/Aile, and X/Zero.

What’s your biggest inspiration when it comes to writing: Other writers, my own imagination that I have no control over, and songs. In that order, maybe I can scrape out something half-decent.

Favorite types of threads: Crack with a strong angst to wash it down and some fluff for dessert. Not necessarily all the same thread, just all happening.

Biggest struggle in regards to your current muse: I kinda talked about this in the favorite muse section, but figuring out scenarios for them to interact in. I’m too timid and careful to take any interesting big chances with them and I feel like what I write with them is kinda boring most of the time. Maybe that’s just me though?

Tagged by: @bluesdln000

Tagging: I honestly have no clue who’s been tagged already or what so if you want to take this feel free

#mun : raine #status : ooc #thank you very much for the tag!#this was fun to write

3 notes · View notes

strykingback · 2 years ago

Text

Zek: Theres no way I can fall in love...

Ivy and Esemeray: *smiles*

Zek: Cyka........

#[The Deadliest Sniper- Zek]#[ERROR 404 FILE NOT FOUND- Crack]#[Random Talking In The HQ- Dash Commentary]

2 notes · View notes

connecticut-seo-adwords · 7 years ago

Text

A Technical SEO Checklist: Fundamentals for 2018

Keeping up with Google's algorithms is a full-time job. In the past year it's cracked down on ad-heavy content (Fred), shaken up local search results (Possum), and completely changed how websites are indexed (mobile-first indexing).

If you forgot to tend to your technical SEO while you were busy surviving Google algorithm updates, I could hardly blame you. Fortunately, there's no time like the present to double-check your site health and conduct an SEO audit.

This checklist will run you through all the technical SEO fundamentals you need in place in the year ahead.

1. Install essential tools

Your ability to improve your SEO hinges on your tools' ability to find and fix technical problems. Here are the absolute essentials you'll need:

Those tools are the absolute bare minimum for improving your technical SEO.

You won't need anything else to follow along in this article, but if you feel you've reached your limit with Google's free tools and you want to step up your SEO game, I highly recommend you consider tools that will let you dig deeper into your analytics. There are a ton of options, so you're sure to find something that suits your needs.

Consider your needs and your budget, and then look for software that lets you...

Monitor your link health, find and fix broken links, and discover new link-building opportunities.

Correct more errors, such as 404/500 error pages, faulty redirects, W3C validation errors, etc.

Perform deeper keyword analysis and optimize for all rankings, including local and geo-specific.

Discover content errors such as thin content, duplicate content, canonicalization errors, etc.

Spy on your competitors and compare backlinks, anchor text, etc.

2. Improve indexing and crawlability

One of the best ways to find out whether your site has too many duplicate URLs, noncanonical URLs, and URLs that contain a noindex metatag is to check your index status.

To do this, enter site:yourdomain.com into your target search engine, use your favorite SEO crawling software, or log in to Google Search Console and click Google Index > Index Status to see your report.

Ideally, you want your total indexed pages as close to your total number of pages as possible.

Note that while manually reviewing your robots.txt will help you discover some disallowed pages, you're liable to miss many others. I recommend a more dedicated tool that will help you find all blocked pages, including those blocked by robots.txt instructions, noindex metatags, and X-Robot-Tag headers.

3. Improve your 'crawl budget'

We call the number of pages on your website that search engine spiders crawl in a given period of time your "crawl budget." You probably won't have to worry about crawl budget (unless your site is gigantic), but working to improve your crawl budget almost always translates into improving your technical SEO.

To view your approximate crawl budget, log in to Google Search Console and click Crawl > Crawl Stats. Unfortunately, finding a page-by-page breakdown of your crawl stats is a little harder and will require a separate tool.

My team recently tested whether it's possible to boost your crawl budget. What we found is a strong correlation between the number of spider hits and external links, which suggests that growing your link profile will also improve your crawl budget.

Building links organically takes time, however. If you want to improve your crawl budget right now while you begin grooming your link profile, I suggest auditing your internal links, fixing broken links, and limiting your use of uncrawlable media-rich files.

Revisiting your URL structure will also improve your crawl budget. Ensure that all of your URLs are as succinct as possible, include 1-2 focused keywords, and easily identify the topic. For example, if this article's URL were "marketingprofs.com/410571591," we might change it to "marketingprofs.com/2018-technical-seo-checklist."

(For more advice, check out this guide to improving your crawl budget.)

4. Clean up your sitemap

You can also boost your crawlability by improving your sitemap navigation. You can check your sitemap for errors by clicking Crawl > Sitemaps in your Google Search Console.

For the sake of technical SEO, you'll want to make sure that your XML sitemap is...

Uncluttered: Remove all noncanonical URLs, redirects, 400-level pages, and blocked pages from your sitemap.

While you're optimizing your XML sitemap for search engines, don't forget to update your HTML sitemaps, too. Doing so will help improve user experience for your site visitors.

5. Optimize metadata

Review your HTML code and improve your meta descriptions and title tags wherever they're missing. Here are some general guidelines you can follow:

Title Tags

The length should be 70-71 characters for desktop, 78 characters for mobile.

Accurately reflect the content on your page.

Lead with your most important keywords, but don't keyword-stuff your title tags.

Insert your brand/company name at the end of your title tags.

Don't duplicate title tags across multiple pages.

Make it different from your H1 headline.

Meta Descriptions

The length should be 200 characters for desktop, 170-172 characters for mobile.

They should be a brief, readable, and unique description of a page's topic.

Naturally insert 1-2 keywords consistent with title tag keywords.

Headline Tags

Tag your main headline with an H1 tag (only one H1 tag per page!).

Use H2 tags for sub-headers or different topics on the same page.

If you use sub-headers within your sub-headers (lists, source links, etc.) use more H3–H6 tags, in descending order.

6. Fix broken links and redirects

After you've performed your website audit, fixing any redirect chains and broken links is among the best bits of technical SEO you can perform. Redirects and broken links eat up valuable crawl budget, slow down your page, result in a poorer user experience, and may ultimately devalue your page. It's in your best interest to fix them ASAP.

Broken Links

Broken internal links are easy enough to fix: Just find the offending page and turn the broken link into a link to an existing page. Try to keep your site structure as shallow as possible so that no page is more than three clicks away from your homepage.

To fix broken external links, you'll have to contact the webmaster and ask them to fix or remove your link. If that's not possible, you may have to set up a 301 redirect to an active page or disavow the dead link (especially if it's from an unreputable source).

Redirect Chains

Fix chains of three or more redirects first, and do what you can to eliminate redirects altogether. Having many redirects in a row might result in search engine spiders' dropping off before they reach the end of the chain, which might result in unindexed pages.

Orphan Pages

You may also discover orphan pages during your SEO audit. These are pages that aren't linked to from any other page of your website. Add links to ensure that visitors and search engines can find that page.

7. Use rich snippets and structured data

Schema markup gives users a snapshot of your content before they click on the page so that they can see thumbnail images, star ratings, and additional product details before clicking on your link.

Rich snippets like this help build consumer trust and often encourage clickthroughs.

Go to Schema.org to learn how to set up structured data for your pages, then use Google's Structured Data Testing Tool to review your snippets.

8. Optimize site speed for mobile

A recent Google study found that visitors are three times more likely to abandon a page with a 1-5-second load time than bounce from a page with a 1-3-second load time.

Site speed has always been one of Google's most important ranking signals, and it's one of the most important technical SEO elements related to your conversions as well.

Unfortunately, slow load times are common, especially on mobile sites. Google's study noted that "the majority of mobile websites are slow and bloated with too many elements," and 70% of pages took nearly seven seconds to load their above-the-fold content.

Here's what you can do to improve your site speed and mobile performance:

Optimize your images.

Minify JavaScript and CSS Files.

Move files such as images, CSS, and Javascript to a CDN (content delivery network).

If you're looking for technical SEO to improve on your page, this is a good place to start. With Google's recent switch to mobile-first indexing, your site ranking will be largely determined by your mobile site's performance.

9. Look to the future (voice search, RankBrain, and more)

Checklists like this are great if you've fallen behind on your technical SEO, but they don't often help you prepare for upcoming trends. So do yourself a favor and brush up on other innovations you can use to solve customer pain points, such as...

Voice search: Local businesses are becoming increasingly discovered via voice chat, through queries such as "I want to buy _____" or "What are _____ businesses near me?" Optimize for voice search to help these customers find you.

RankBrain/AI: RankBrain allows Google to understand what would be the best result for the user's query, based on historical data. The algorithm is focused on quality for the end-user, so optimize the experience for the audience that you want coming to your website.

Accelerated Mobile Pages (AMP), mobile apps, and progressive Web apps (PWA): As mobile usage increases and Google shifts toward mobile-first indexing, developers are working hard to make the mobile Web as efficient and useful as possible.

* * *

Studies show that after performing a major site audit, 39% of SEOs tackle technical SEO first. Improving your technical SEO is great, because it gives you a bedrock upon which to build everything else, but don't forget about other SEO elements in the process.

At the end of the day, you still need great content, you still need to build citations in prominent directories, and you still need to build up a strong social media presence.

Make sure every part of your website is working together to establish you as an authority in your niche and improve your Web presence.

Join over 600,000 marketing professionals, and gain access to thousands of marketing resources! Don't worry ... it's FREE!

Source

https://www.marketingprofs.com/articles/2017/33236/your-2018-technical-seo-checklist

0 notes

readersforum · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

New Post has been published on http://www.readersforum.tk/uncovering-seo-opportunities-via-log-files/

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo to get your very own tailored walkthrough of STAT.

0 notes

tranlinhlan · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/2Uadn11) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

via Blogger http://bit.ly/2CD2HRA

0 notes

isearchgoood · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/eSXNch) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

via Blogger http://bit.ly/2MuSBGF #blogger #bloggingtips #bloggerlife #bloggersgetsocial #ontheblog #writersofinstagram #writingprompt #instapoetry #writerscommunity #writersofig #writersblock #writerlife #writtenword #instawriters #spilledink #wordgasm #creativewriting #poetsofinstagram #blackoutpoetry #poetsofig

0 notes

strykingback · 1 year ago

Text

"UWAAAAAAAAAAAAAAAGH!!!! SEEEEEEEEEEEEEEEEEEEX!!!!!!!! SEEEEEEEEEEEEEEEEEEEX!!!!!" Louvel would scream while running out of a tunnel at speeds up to mach 100. Wait what-?

#[A Strykers Edge- Blade]#[Random Talking In The HQ- Dash Commentary]#[ERROR 404 FILE NOT FOUND- Crack]

0 notes

tracisimpson · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

#The Moz Blog Blogger

0 notes

lawrenceseitz22 · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/eSXNch) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

from Blogger http://bit.ly/2TbHGnS via IFTTT

#IFTTT #Blogger

0 notes

swunlimitednj · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/eSXNch) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

from Blogger http://bit.ly/2Mqe17S via SW Unlimited

0 notes

neilmberry · 6 years ago

Text

Uncovering SEO Opportunities via Log Files

Posted by RobinRozhon

I use web crawlers on a daily basis. While they are very useful, they only imitate search engine crawlers’ behavior, which means you aren’t always getting the full picture.

Log file analysis may discover URLs on your site that you had no idea about but that search engines are crawling anyway — a major waste of Google server resources (Google Webmaster Blog):

“Wasting server resources on pages like these will drain crawl activity from pages that do actually have value, which may cause a significant delay in discovering great content on a site.”

There’s still a huge value in analyzing logs produced from those crawls, though. It will show what pages Google is crawling and if anything needs to be fixed.

What are server logs?

Analyzing logs is not rocket science — the logic is the same as when working with tables in Excel or Google Sheets. The hardest part is getting access to them — exporting and filtering that data.

Looking at a log file for the first time may also feel somewhat daunting because when you open one, you see something like this:

Calm down and take a closer look at a single line:

66.249.65.107 - - [08/Dec/2017:04:54:20 -0400] "GET /contact/ HTTP/1.1" 200 11179 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

You’ll quickly recognize that:

66.249.65.107 is the IP address (who)

[08/Dec/2017:04:54:20 -0400] is the Timestamp (when)

GET is the Method

/contact/ is the Requested URL (what)

200 is the Status Code (result)

11179 is the Bytes Transferred (size)

“-” is the Referrer URL (source) — it’s empty because this request was made by a crawler

Mozilla/5.0 (compatible; Googlebot/2.1; +http://bit.ly/eSXNch) is the User Agent (signature) — this is user agent of Googlebot (Desktop)

Once you know what each line is composed of, it’s not so scary. It’s just a lot of information. But that’s where the next step comes in handy.

Tools you can use

Start analyzing

Here are a few samples of questions I use at the start of my analysis:

Which search engines crawl my website?

Which URLs are crawled most often?

Which content types are crawled most often?

Which status codes are returned?

If you see that Google is crawling non-existing pages (404), you can start asking which of those requested URLs return 404 status code.

If you use a CDN or cache server, you need to get that data as well to get the full picture.

Segment your data

There are various ways to group URLs:

Group by content type (single product pages vs. category pages)

Group by language (English pages vs. French pages)

Group by storefront (Canadian store vs. US store)

Group by file format (JS vs. images vs. CSS)

Don’t forget to slice your data by user-agent. Looking at Google Desktop, Google Smartphone, and Bing all together won’t surface any useful insights.

Monitor behavior changes over time

By analyzing server logs twice a year, at the very least, you’ll surface changes in crawler’s behavior.

Watch for spoofing

Spambots and scrapers don’t like being blocked, so they may fake their identity — they leverage Googlebot’s user agent to avoid spam filters.

To verify if a web crawler accessing your server really is Googlebot, you can run a reverse DNS lookup and then a forward DNS lookup. More on this topic can be found in Google Webmaster Help Center.

Merge logs with other data sources

Blend server logs with multiple other sources such as Google Analytics data, keyword ranking, sitemaps, crawl data, and start asking questions like:

What pages are not included in the sitemap.xml but are crawled extensively?

What pages are included in the Sitemap.xml file but are not crawled?

Are revenue-driving pages crawled often?

Is the majority of crawled pages indexable?

You can see more examples of blending log files with other data sources in my post about advanced log analysis.

Use logs to debug Google Analytics

Don’t think of server logs as just another SEO tool. Logs are also an invaluable source of information that can help pinpoint technical errors before they become a larger problem.

Using log files in conjunction with keyword tracking in STAT helped us uncover the whole story and diagnose this issue quickly.

Putting it all together

Log analysis is a must-do, especially once you start working with large websites.

Want more?

Ready to learn how to get cracking and tracking some more? Reach out and request a demo get your very own tailored walkthrough of STAT.

Uncovering SEO Opportunities via Log Files published first on http://elitelimobog.blogspot.com

0 notes