Difference between revisions of "Frontend"

From Seobility Wiki
Jump to: navigation, search
(→‎Similar articles)
(→‎Structured data and accessibility)
 
(17 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
<seo title="What is frontend?" metadescription="The frontend covers everything users of a website can see, touch, and experience. But what makes an SEO-friendly frontend?" />
+
<seo title="What is Frontend? Definition and Explanation" metadescription="Frontend and backend are two terms used in software development. The frontend covers everything you can see, touch, and experience. Learn more ..." />
  
 
== Definition ==
 
== Definition ==
Line 6: Line 6:
  
 
== Distinguishing frontend from backend ==
 
== Distinguishing frontend from backend ==
−
 
 
[[File:Frontend-vs-Backend.png|thumb|450px|right|alt=Distinguishing Frontend from Backend|'''Figure:''' Frontend vs. Backend - Author: Seobility - License: [[Creative Commons License BY-SA 4.0|CC BY-SA 4.0]]|link=https://www.seobility.net/en/wiki/images/0/04/Frontend-vs-Backend.png]]
 
[[File:Frontend-vs-Backend.png|thumb|450px|right|alt=Distinguishing Frontend from Backend|'''Figure:''' Frontend vs. Backend - Author: Seobility - License: [[Creative Commons License BY-SA 4.0|CC BY-SA 4.0]]|link=https://www.seobility.net/en/wiki/images/0/04/Frontend-vs-Backend.png]]
  
−
“Backend” refers to everything users of a software or website cannot see in their browser. This includes, for example, servers that host websites. A database that stores user input data or website content can also be assigned to the back end. In case of a website, the internet connects frontend and backend. In content management systems, the terms frontend and backend can refer to the end-user interface of the CMS and the administration area. Scripting languages like Node.js, PHP, or Python and compiled languages like C# and Java work in the backend. Authentication and authorization also take place in the backend.
+
“Backend” refers to everything users of a software or website cannot see. This includes, for example, servers that host websites. A database that stores user input data or website content can also be assigned to the back end. In case of a website, the internet connects frontend and backend. In [[Content Management System (CMS)|content management systems]], the terms frontend and backend can refer to the end-user interface of the CMS and the administration area. Authentication and authorization take place in the backend.
  
 
== What makes an SEO-friendly frontend? ==
 
== What makes an SEO-friendly frontend? ==
  
−
An SEO-friendly frontend starts with optimal usability. Users who can easily navigate through a website tend to stay longer and rarely abort their visit. This is important for the ranking of your website because dwell times and bounce rates are important evaluation criteria for Google. Below we explain a few factors that contribute to an SEO-friendly frontend and thus influence your website’s usability and ranking on Google.
+
Users who can easily navigate through a website tend to stay longer and rarely abort their visit. This is important for the ranking of your website because [[Dwell Time|dwell times]] and bounce rates are important evaluation criteria for Google. Below we explain a few factors that contribute to an SEO-friendly frontend and thus influence your website’s usability and ranking on Google.
  
 
=== Clean and semantic HTML code ===
 
=== Clean and semantic HTML code ===
  
−
Clean and semantically flawless HTML code is the basic requirement for an SEO-friendly frontend. Errors in your HTML code can be the reason why [[Search Engine Crawlers|search engine robots]] cannot crawl a page and therefore cannot index it.
+
Clean and semantically flawless HTML code is the basic requirement for an SEO-friendly frontend. Errors in your HTML code can be the reason why [[Search Engine Crawlers|search engine robots]] cannot crawl a page and therefore cannot [[indexing|index]] it.
 +
 
 +
=== Avoid framesets and Flash content ===
  
−
=== Unique Content ===
+
[[Frames and framesets|Framesets]] and Flash content is deprecated and should no longer be used for a website today.
  
−
Unique content means that you shouldn’t have multiple web pages with the same content or material from other websites. Otherwise, search engines cannot decide which of the pages with identical entries is more relevant to a search query and should be indexed. If duplicate content is unavoidable, you can use [[Canonical Tag|canonical tags]] to point search engine bots to the original page you want to have indexed.
+
=== Page loading speed ===
  
−
=== Avoid framesets and Flash content ===
+
Visitors often leave a website very quickly if it is not loading fast enough. Three seconds is usually the maximum acceptable loading time with 200ms being the optimal speed. For mobile websites, a fast display of "[[Above the Fold|above the fold]]" content plays an important role. Webmasters can test the [[Page Speed|page speed]] of their website with the free tool [https://developers.google.com/speed/pagespeed/insights/ "PageSpeed Insights"] from Google.
  
−
[[Frames and framesets|Framesets]] and Flash content should no longer be used for a website today. Search engines cannot crawl this content and therefore cannot index it. Server-side techniques used on the backend are better for outsourcing content from a website.
+
=== Responsive Design ===
  
−
=== Page Title and Meta-Description ===
+
In addition to loading speed, Responsive Design also plays an important role when it comes to good frontend. Especially in times of [[Mobile First|mobile first]], consumers use devices with different sizes and displays. Therefore, websites and images should always be designed in such a way that they are optimally suited for all [[Viewport|viewports]]. This not only helps (mobile) users but also makes it easier for search engine bots to crawl a website.
  
−
Create individual [[Meta Title|titles]] and [[Meta Description|descriptions]] for each page of your website. This metadata helps Google and other search engines understand and rank the content of a page.
+
=== Structured data and accessibility ===
  
−
=== Page loading speed ===
+
Good markup and structured data - just like Responsive Web Design - help search engine crawlers navigate and index pages. In addition, structured data enables the display of star ratings, prices, recipes, and <html><a href="https://www.seobility.net/en/blog/rich-snippets/" target="_blank">rich snippets</a></html> in the SERPs. Responsive snippets, in turn, can positively influence the [[CTR (Click-Through Rate)|click-through rate]].
  
−
Visitors often leave a website very quickly if it is not loading fast enough. Three seconds is usually the maximum acceptable loading time. For mobile websites, a fast display of "above the fold" content plays an important role. Webmasters can test the [[Page Speed|page speed]] of their website with the free tool "PageSpeed Insights" from Google.
+
Not only search engines benefit from structured data and optimized markup, but such optimizations are also important for impaired persons. Tools such as screen readers work similar to crawlers and use this structured data to describe the content of a website. In this context, alt and title attributes of images and links also play an important role and should not be missing.
  
 
=== Breadcrumb navigation ===
 
=== Breadcrumb navigation ===
  
−
For websites with many subpages or online shops with numerous categories and subcategories, breadcrumb navigation can make orientation easier for visitors. Breadcrumb navigation is an additional navigation scheme that is added at the top of a page in frontend design. This has the advantage that users always know their current location on a website. In addition, they can switch to a higher-level or already visited page with just one click, without having to use the back button in their browser or start over at the top navigation level.
+
For websites with many subpages or online shops with numerous categories and subcategories, [[Breadcrumb Navigation|breadcrumb navigation]] can make orientation easier for visitors. Breadcrumb navigation is an additional navigation scheme that is added at the top of a page in frontend design. This has the advantage that users always know their current location on a website. In addition, they can switch to a higher-level or already visited page with just one click, without having to use the back button in their browser or start over at the top navigation level.
  
 
=== Internal linking ===
 
=== Internal linking ===
  
 
Connecting a website’s pages with [[Internal Linking|internal links]] helps search engines understand the structure of a website and capture all its subpages. Internal links also make it easier for users to find additional information, which increases their dwell time on your site. If you want to prevent search engine bots from following certain links, you can add nofollow tags to these links.
 
Connecting a website’s pages with [[Internal Linking|internal links]] helps search engines understand the structure of a website and capture all its subpages. Internal links also make it easier for users to find additional information, which increases their dwell time on your site. If you want to prevent search engine bots from following certain links, you can add nofollow tags to these links.
−
 
−
=== Robots.txt ===
 
−
 
−
Use a "[[Robots.txt|robots.txt]]" file in frontend development to tell search engines which pages of your website should not be crawled. Excluding pages like your imprint or privacy policy saves your website’s crawl budget. This ensures that only your most important pages are crawled and indexed. To make sure that search engines can find and use your “robots.txt” file, you have to save it in the top directory of your server.
 
−
 
−
=== XML sitemap ===
 
−
 
−
For large websites, you should create an XML sitemap file containing a list of all existing subpages and submit it to Google using the search console. This sitemap helps search engine robots crawl large websites completely and accelerates the indexing process. An HTML sitemap, on the other hand, makes it easier for users to navigate through your website.
 
  
 
=== Search engine friendly URLs ===
 
=== Search engine friendly URLs ===
Line 66: Line 59:
 
[[Category:Web Design]]
 
[[Category:Web Design]]
 
[[Category:Web Development]]
 
[[Category:Web Development]]
 +
 +
<html><script type="application/ld+json">
 +
    {
 +
      "@context": "https://schema.org/",
 +
      "@type": "ImageObject",
 +
      "contentUrl": "https://www.seobility.net/en/wiki/images/0/04/Frontend-vs-Backend.png",
 +
      "license": "https://creativecommons.org/licenses/by-sa/4.0/",
 +
      "acquireLicensePage": "https://www.seobility.net/en/wiki/Creative_Commons_License_BY-SA_4.0"
 +
    }
 +
    </script></html>
 +
 +
{| class="wikitable" style="text-align:left"
 +
|-
 +
|'''About the author'''
 +
|-
 +
| [[File:Seobility S.jpg|link=|100px|left|alt=Seobility S]] The Seobility Wiki team consists of seasoned SEOs, digital marketing professionals, and business experts with combined hands-on experience in SEO, online marketing and web development. All our articles went through a multi-level editorial process to provide you with the best possible quality and truly helpful information. Learn more about <html><a href="https://www.seobility.net/en/wiki/Seobility_Wiki_Team" target="_blank">the people behind the Seobility Wiki</a></html>.
 +
|}
 +
 +
<html><script type="application/ld+json">
 +
{
 +
  "@context": "https://schema.org",
 +
  "@type": "Article",
 +
  "author": {
 +
    "@type": "Organization",
 +
    "name": "Seobility",
 +
    "url": "https://www.seobility.net/"
 +
  }
 +
}
 +
</script></html>

Latest revision as of 12:01, 26 March 2024

Definition

Frontend and backend are two terms used in software development. The frontend covers everything the user of a software or website can see, touch, and experience. On websites, the frontend includes content (posts, pages, media, and comments), design, and navigation. Another example would be the frontend of database software, where users can enter and display data.

Distinguishing frontend from backend

Distinguishing Frontend from Backend
Figure: Frontend vs. Backend - Author: Seobility - License: CC BY-SA 4.0

“Backend” refers to everything users of a software or website cannot see. This includes, for example, servers that host websites. A database that stores user input data or website content can also be assigned to the back end. In case of a website, the internet connects frontend and backend. In content management systems, the terms frontend and backend can refer to the end-user interface of the CMS and the administration area. Authentication and authorization take place in the backend.

What makes an SEO-friendly frontend?

Users who can easily navigate through a website tend to stay longer and rarely abort their visit. This is important for the ranking of your website because dwell times and bounce rates are important evaluation criteria for Google. Below we explain a few factors that contribute to an SEO-friendly frontend and thus influence your website’s usability and ranking on Google.

Clean and semantic HTML code

Clean and semantically flawless HTML code is the basic requirement for an SEO-friendly frontend. Errors in your HTML code can be the reason why search engine robots cannot crawl a page and therefore cannot index it.

Avoid framesets and Flash content

Framesets and Flash content is deprecated and should no longer be used for a website today.

Page loading speed

Visitors often leave a website very quickly if it is not loading fast enough. Three seconds is usually the maximum acceptable loading time with 200ms being the optimal speed. For mobile websites, a fast display of "above the fold" content plays an important role. Webmasters can test the page speed of their website with the free tool "PageSpeed Insights" from Google.

Responsive Design

In addition to loading speed, Responsive Design also plays an important role when it comes to good frontend. Especially in times of mobile first, consumers use devices with different sizes and displays. Therefore, websites and images should always be designed in such a way that they are optimally suited for all viewports. This not only helps (mobile) users but also makes it easier for search engine bots to crawl a website.

Structured data and accessibility

Good markup and structured data - just like Responsive Web Design - help search engine crawlers navigate and index pages. In addition, structured data enables the display of star ratings, prices, recipes, and rich snippets in the SERPs. Responsive snippets, in turn, can positively influence the click-through rate.

Not only search engines benefit from structured data and optimized markup, but such optimizations are also important for impaired persons. Tools such as screen readers work similar to crawlers and use this structured data to describe the content of a website. In this context, alt and title attributes of images and links also play an important role and should not be missing.

Breadcrumb navigation

For websites with many subpages or online shops with numerous categories and subcategories, breadcrumb navigation can make orientation easier for visitors. Breadcrumb navigation is an additional navigation scheme that is added at the top of a page in frontend design. This has the advantage that users always know their current location on a website. In addition, they can switch to a higher-level or already visited page with just one click, without having to use the back button in their browser or start over at the top navigation level.

Internal linking

Connecting a website’s pages with internal links helps search engines understand the structure of a website and capture all its subpages. Internal links also make it easier for users to find additional information, which increases their dwell time on your site. If you want to prevent search engine bots from following certain links, you can add nofollow tags to these links.

Search engine friendly URLs

When it comes to frontend design, people often forget that not only search engines crawl a web page’s URL, but users also read it. This is why you should keep URLs short, descriptive and easy to read. Avoid special characters such as underscores, ampersands, and percent signs. The easier it is to read a URL, the more positive it will be in terms of both usability and search engine optimization.

Related links

Similar articles

About the author
Seobility S
The Seobility Wiki team consists of seasoned SEOs, digital marketing professionals, and business experts with combined hands-on experience in SEO, online marketing and web development. All our articles went through a multi-level editorial process to provide you with the best possible quality and truly helpful information. Learn more about the people behind the Seobility Wiki.