De essentiële gids van SEO voor webtechnologie Zoekmachine Watch


De essentiële gids van SEO voor webtechnologie

Als een SEO-professional zal uw rol u steevast leiden naar interacties met mensen in een groot aantal verschillende rollen, waaronder bedrijfseigenaars, marketingmanagers, makers van inhoud, linkbuilders, PR-bureaus en ontwikkelaars.

Die laatste - ontwikkelaars - is een verzamelnaam die softwaretechnici, coders, programmeurs, ontwikkelaars van voor- en achterkant en IT-professionals van verschillende typen kan omvatten. Dit zijn de mensen die de code schrijven en / of in het algemeen de onderliggende verschillende webtechnologieën beheren die websites bevatten en van stroom voorzien.

In uw rol als SEO kan het al dan niet praktisch zijn om programmeertalen volledig te beheersen, zoals C ++ en Java, of scriptalen zoals PHP en JavaScript, of opmaaktalen zoals HTML, XML of CSS voor stijlbladen .

En er zijn veel meer programmeer-, scripting- en markup-talen die er zijn - het zou een enorme opgave zijn om een ​​meester te zijn in elke taal, zelfs als je een voltijdse programmeur bent en geen SEO.

Maar het is essentieel voor u als SEO-professional om de verschillende talen en technologieën en technologiestapels die het internet omvat, te begrijpen. Wanneer u SEO-aanbevelingen doet, welke ontwikkelaars het meest waarschijnlijk zullen worden uitgevoerd, moet u hun manier van denken, hun pijnpunten, hun werktaak begrijpen en moet u hun taal kunnen spreken.

U hoeft niet alles te weten wat ontwikkelaars weten, maar u moet goed begrijpen wat ontwikkelaars doen, zodat u betere vragen kunt stellen en SEO-aanbevelingen kunt geven op een manier die bij hen past, en die aanbevelingen worden eerder uitgevoerd als gevolg.

Wanneer je hun taal spreekt en begrijpt hoe hun wereld is, draag je bij aan een samenwerkingsomgeving waarin iedereen aan dezelfde kant van het touw trekt voor dezelfde positieve resultaten.

En natuurlijk, naast het opbouwen van samenwerkingsrelaties, is professioneel zijn een heleboel technisch detectivewerk en probleemdetectie en -preventie, dus het begrijpen van verschillende aspecten van webtechnologie is niet optioneel; het is verplicht.

Webtechnologie kan ingewikkeld en intimiderend zijn, maar hopelijk helpt deze gids u de dingen een beetje gemakkelijker te maken en vult u enkele opmerkingen in.

Laten we meteen naar binnen springen!

Het internet versus het World Wide Web

De meeste mensen gebruiken deze termen door elkaar, maar technisch gezien betekenen de twee termen niet hetzelfde, hoewel ze wel verwant zijn.

Het internet begon als een gedecentraliseerd netwerk van onafhankelijke onderling verbonden computers.

Het Amerikaanse ministerie van Defensie was in de loop van de tijd betrokken bij en bekroonde contracten, onder meer voor de ontwikkeling van het ARPANET-project (Advanced Research Projects Agency Network), een netwerk voor vroege pakketwisseling en als eerste om TCP / IP (Transmission Control Protocol en Internet Protocol) te gebruiken ).

Het ARPANET project heeft geleid tot “ internet werken ", waar verschillende netwerken van computers kunnen worden samengevoegd tot een groter “netwerk van netwerken".

De ontwikkeling van het World Wide Web is in de jaren tachtig gecrediteerd aan de Britse computerwetenschapper Sir Tim Beners-Lee; hij ontwikkelde het koppelen van hypertextdocumenten, wat resulteerde in een model voor het delen van informatie dat "bovenop" van internet werd gebouwd.

Documents (web pages) were specified to be formatted in a markup language called “HTML" (Hypertext Markup Language), and could be linked to each other using “hyperlinks" that users could click to navigate to other web pages.

Further reading:

Web hosting

Web hosting, or hosting for short, are services that allow people and businesses to put a web page or a website on the internet. Hosting companies have banks of computers called “servers" that are not entirely dissimilar in nature to computers you’re already familiar with, but of course there are differences.

There are various types of web hosting companies that offer a range of services in addition to web hosting; such services may include domain name registration, website builders, email addresses, website security services, and more.

In short, a host is where websites are published.

Further reading:

Web servers

A web server is a computer that stores web documents and resources. Web servers receive requests from clients (browsers) for web pages, images, etc. When you visit a web page, your browser requests all the resources/files needed to render that web page in your browser. It goes something like this:

Client (browser) to server: “Hey, I want this web page, please provide all the text, images and other stuff you have for that page."

Server to client: “Okay, here it is."

Various factors impact how quickly the web page will display (render) including the speed of the server and the size(s) of the various files being requested.

There are three server types you’ll most often encounter:

  1. Apache is open-source, free software compatible with many operating systems such as Linux. An often-used acronym is “LAMP stack" referring to a bundling of Linux, Apache, MySQL (relational database) and PHP (a server-side scripting language).
  2. IIS stands for “Internet Information Services" and is proprietary software made by Microsoft. An IIS server is often referred to as a “Windows Server" because it runs on Windows NT operating systems.
  3. NGINX – pronounced “Engine X", is billed as a high-performance server able to also handle load balancing, used as a reverse proxy, and more. Their stated goals and reason for being include outperforming other types of servers.

Further reading:

Server log files

Often shortened to “log files", these are records of sever activity in response to requests made for web pages and associated resources such as images. Some servers may already be configured to record this activity, others will need to be configured to do so.

Log files are the “reality" of what’s happening with a website and will include information such as the page or file requested, date and time stamp of the request, the user agent making the request, the response type (found, error, redirected, etc.), the referrer, and a few other items such as bytes served and client IP address.

SEOs should get familiar with parsing log files. To go into this topic in more detail, read JafSoft’s explanation of a web server log file sample.

FTP

FTP stands for File Transfer Protocol, and it’s how you upload resource files such as webpages, images, XML Sitemaps, robots.txt files, and PDF files to your web hosting account to make these resource files available and viewable on the Web via browsers. There are free FTP software programs you can use for this purpose.

The interface is a familiar file-folder tree structure where you’ll see your local machine’s files on the left, and the remote server’s files on the right. You can drag and drop local files to the server to upload. Voila, you’ve put files onto the internet! For more detail, Wired has an excellent guide on FTP for beginners.

Domain name

A domain name is a string of (usually) text and is used in a URL (Uniform Resource Locator). Keeping this simple, for the URL https://www.website.com, “website" is the domain name. For more detail, check out the Wikipedia article on domain names.

Root domain & subdomain

A root domain is what we commonly think of as a domain name such as “website" in the URL https://www.website.com. A subdomain is the www. part of the URL. Other examples of subdomains would be news.website.com, products.website.com, support.website.com and so on.

For more information on the difference between a domain and a subdomain, check out this video from HowTech.

URL vs. URI

URL stands for “Universal Resource Locator" (such as https://www.website.com/this-is-a-page) and URI stands for “Uniform Resource Identifier" and is a subset of a full URL (such as /this-is-a-page.html). More info here.

HTML, CSS, and JavaScript

I’ve grouped together HTML, CSS, and JavaScript here not because each don’t deserve their own section here, but because it’s good for SEOs to understand that those three languages are what comprise much of how modern web pages are coded (with many exceptions of course, and some of those will be noted elsewhere here).

HTML stands for “Hypertext Markup Language", and it’s the original and foundational language of web pages on the World Wide Web.

CSS stands for “Cascading Style Sheets" and is a style sheet language used to style and position HTML elements on a web page, enabling separation of presentation and content.

JavaScript (not to be confused with the programming language “Java") is a client-side scripting language to create interactive features on web pages.

Further reading:

AJAX & XML

AJAX stands for “Asynchronous JavaScript And XML. Asynchronous means the client/browser and the server can work and communicate independently allowing the user to continue interaction with the web page independent of what’s happening on the server. JavaScript is used to make the asynchronous server requests and when the server responds JavaScript modifies the page content displayed to the user. Data sent asynchronously from the server to the client is packaged in an XML format, so it can be easily processed by JavaScript. This reduces the traffic between the client and the server which increases response time and speed.

XML stands for “Extensible Markup Language" and is similar to HMTL using tags, elements, and attributes and was designed to both store and transport data, whereas HTML is used to display data. For the purposes of SEO, the most common usage of XML is in XML Sitemap files.

Structured data (AKA, Schema.org)

Structured data is markup you can add to the HTML of a page to help search engines better understand the content of the page, or at least certain elements of that page. By using the approved standard formats, you provide additional information that makes it easier for search engines to parse the pertinent data on the page.

Common uses of structured data are to markup certain aspects of recipes, literary works, products, places, events of various types, and much more.

Schema.org was launched on June 2, 2011, as a collaborative effort by Google, Bing and Yahoo (soon after joined by Yandex) to create a common set of agreed-upon and standardized set of schemas for structured data markup on web pages. Since then, the term “Schema.org" has become synonymous with the term “structured data", and Schema.org structured data types are continually evolving with new types being added with relative frequency.

One of the main takeaways about structured data is that it helps disambiguate data for search engines so they can more easily understand information and data, and that certain marked-up elements may result in additional information being displayed in Search Engines Results Pages (SERPs), such as review stars, recipe cooking times, and so on. Note that adding structured data is not a guarantee of such SERP features.

There are a number of structured data vocabularies that exist, but JSON-LD (JavaScript Object Notation for Linked Data) has emerged as Google’s preferred and recommended method of doing structured data markup per the Schema.org guidelines, but other formats are also supported such as microdata and RDFa.

JSON-LD is easier to add to pages, easier to maintain and change, and less prone to errors than microdata which must be wrapped around existing HML elements, whereas JSON-LD can be added as a single block in the HTML head section of a web page.

Here is the Schema.org FAQ page for further investigation – and to get started using microdata, RDFa and JSON-LD, check out our complete beginner’s guide to Schema.org markup.

Front-end vs. back-end, client-side vs. server-side

You may have talked to a developer who said, “I’m a front-end developer" and wondered what that meant. Of you may have heard someone say “oh, that’s a back-end functionality". It can seem confusing what all this means, but it’s easily clarified.

“Front-end" and “client-side" both mean the same thing: it happens (executes) in the browser. For example, JavaScript was originally developed as something that executed on a web page in the browser, and that means without having to make a call to the server.

“Back-end" and “server-side" both mean the same thing: it happens (executes) on a server. For example, PHP is a server-side scripting language that executes on the server, not in the browser. Some Content Management Systems (CMS for short) like WordPress use PHP-based templates for web pages, and the content is called from the server to display in the browser.

Programming vs. scripting languages

Engineers and developers do have differing explanations and definitions of terms. Some will say ultimately there’s no differences or that the lines are blurry, but the generally accepted difference between a programming language (like C or Pascal) vs. a scripting language (like JavaScript or PHP) is that a programming language requires an explicit compiling step, whereas human-created, human-readable code is turned into a specific set of machine-language instructions understandable by a computer.

Content Management System (CMS)

A CMS is a software application or a set of related programs used to create and manage websites (or we can use the fancy term “digital content"). At the core, you can use a CMS to create, edit, publish, and archive web pages, blog posts, and articles and will typically have various built-in features.

Using a CMS to create a website means that there is no need to create any code from scratch, which is one of the main reasons CMS’ have broad appeal.

Another common aspect of CMS’ are plugins, which can be integrated with the core CMS to extend functionalities which are not part of the core CMS feature list.

Common CMS’ include WordPress, Drupal, Joomla, ExpressionEngine, Magento, WooCommerce, Shopify, Squarespace, and there are many, many others.

Read more here about Content Management Systems.

Content Delivery Network (CDN)

Sometimes called a “Content Distribution Network", CDNs are large networks of servers which are geographically dispersed with the goal of serving web content from a server location closer to the client making the request in order to reduce latency (transfer delay).

CDNs cache copies of your web content across these servers, and then servers nearest to the website visitor serve the requested web content. CDNs are used to provide high availability along with high performance. More info here.

HTTPS, SSL, and TLS

Web data is passed between computers via data packets of code. Clients (web browsers) serve as the user interface when we request a web page from a server. HTTP (hypertext transfer protocol) is the communication method a browser uses to “talk to" a server and make requests. HTTPS is the secure version of this (hypertext transfer protocol secure).

Website owners can switch their website to HTTPS to make the connection with users more secure and less prone to “man in the middle attacks" where a third party intercepts or possibly alters the communication.

SSL refers to “secure sockets layer" and is a standard security protocol to establish communication encryption between the server and the browser. TLS, Transport Layer Security, is a more-recent version of SSL

HTTP/1.1 & HTTP/2

When Tim Berners-Lee invented the HTTP protocol in 1989, the computer he used did not have the processing power and memory of today’s computers. A client (browser) connecting to a server using HTTP/1.1 receives information in a sequence of network request-response transactions, which are often referred to as “round trips" to the server, sometimes called “handshakes".

Each round trip takes time, and HTTPS is an HTTP connection with SSL/TSL layered in which requires yet-another handshake with the server. All of this takes time, causing latency. What was fast enough then is not necessarily fast enough now.

HTTP/2 is the first new version of HTTP since 1.1. Simply put, HTTP/2 allows the server to deliver more resources to the client/browser faster than HTTP/1.1 by utilizing multiplexing, compression, request prioritization, and server push which allows the server to send resources to the client that have not yet been requested.

Further reading:

Application Programming Interface (API)

Application is a general term that, simply put, refers to a type of software that can perform specific tasks. Applications include software, web browsers, and databases.

An API is an interface with an application, typically a database. The API is like a messenger that takes requests, tells the system what you want, and returns the response back to you.

If you’re in a restaurant and want the kitchen to make you a certain dish, the waiter who takes your order is the messenger that communicates between you and the kitchen, which is analogous to using an API to request and retrieve information from a database. For more info, check out Wikipedia’s Application programming interface page.

AMP, PWA, and SPA

If you want to build a website today, you have many choices.

You can build it from scratch using HTML for content delivery along with CSS for look and feel and JavaScript for interactive elements.

Or you could use a CMS (content management system) like WordPress, Magento, or Drupal.

Or you could build it with AMP, PWA, or SPA.

AMP stands for Accelerated Mobile Pages and is an open source Google initiative which is a specified set of HTML tags and various functionality components which are ever-evolving. The upside to AMP is lightning-fast loading web pages when coded according to AMP specifications, the downside is some desired features may not be currently supported, and issues with proper analytics tracking.

Further reading:

PWA stands for Progressive Web App, and it blends the best of both worlds between traditional websites and mobile phone apps. PWAs deliver a native app-like experience to users such as push notifications, the ability to work offline, and create a start icon on your mobile phone.

By using “service workers" to communicate between the client and server, PWAs combines fast-loading web pages with the ability to act like a native mobile phone app at the same time. However, because PWAs are JavaScript frameworks, you may encounter a number of technical challenges.

Further reading:

SPAs – Single Page Applications – are different from traditional web pages which load each page a user requests in a session via repeated communications with the server. SPAs, by contrast, run inside the browser and new pages viewed in a user session don’t require page reloading via server requests.

The primary advantages of SPAs include streamlined and simplified development, and a very fast user experience. The primary disadvantages include potential problems with SEO, due to search engines’ inconsistent ability to parse content served by JavaScript. Debugging issues can also be more difficult and take up more developer time.

It’s worth noting that future success of each of these web technologies ultimately depends on developer adoption.

Conclusion

Obviously, it would require a very long book to cover each and every bit of web technology, and in sufficient detail, but this guide should provide you, the professional SEO, with helpful info to fill in some of the blanks in your understanding of various key aspects of web technology.

I’ve provided many links in this article that serve as jumping off points for any topics you would like to explore further. There’s no doubt that there are many more topics SEOs need to be conversant with, such as robots.txt files, meta robots tags, rel canonical tags, XML Sitemaps, server response codes, and much more.

In closing, here’s a nice article on the Stanford website titled “How Does The Internet Work?" that you might find interesting reading; you can find that here.

David Portney is Senior SEO Manager at 3Q Digital

Want to stay on top of the latest search trends?

Get top insights and news from our search experts.

Related reading

Overcoming 4 black hat SEO techniques that spammers and scammers use to harm your search rankings

The dark side of SEO can be crippling to a business if they aren’t aware of how to fight back. Here are four negative (or black hat) SEO tactics to keep a keen eye out for, and how you can protect your site – and your business – from being a victim.

Development SEO 21 Feb 18 |

4 local SEO strategies for small and medium businesses

For small and medium businesses who want to compete on the same playing-field as much larger corporations with greater resources at their disposal, having a strong local SEO strategy is crucial.

Local SEO 20 Feb 18 |

How can you determine your website’s authority, and what can you do to improve it?

The Domain Authority metric was developed by Moz as a means of quantifying your website's relative importance as a whole - its authority. Like most SEO metrics, this number fluctuates based on several factors, and to improve your authority, you first need to determine where your website stands among the others online.

SEO 20 Feb 18 |

How videos generate quick SEO results

You might not be a media and content-oriented company, but you should still consider the perks of having videos for your products and services. According to MWP, online video now accounts for half of all traffic on mobile alone, and 59% of senior executives say that they will opt for video when given the choice between video and text.

SEO Video 19 februari 18 |


Source: searchenginewatch.com