Skip to content

Instantly share code, notes, and snippets.

@niksmac
Last active September 19, 2023 07:08
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save niksmac/9c5126d461d1e1569dd291e504107926 to your computer and use it in GitHub Desktop.
Save niksmac/9c5126d461d1e1569dd291e504107926 to your computer and use it in GitHub Desktop.
Bare minimum SEO Guidelines for launching a website

Basic technical SEO guidelines for a webpage:

  1. Unique H1 Tag: Ensure there's only one H1 tag per page, which typically represents the main heading or topic of the page.
  2. Hierarchical Use of Heading Tags: Use H tags (H1 to H6) in a hierarchical manner. H1 for main topics, H2 for subtopics, H3 for further subtopics, and so on.
  3. Distributed Use of Headings: Use H2, H3, H4, etc., tags appropriately to break down content into readable and organized sections.
  4. Meta Description and Titles:
    • Title Tag: Ensure each page has a unique and descriptive title that's within 50-60 characters.
    • Meta Description: Write a concise summary of the page's content within 150-160 characters. It should be unique for each page.
  5. Social Media Integration: Incorporate social sharing buttons or links to improve visibility and shareability.
  6. URL Structure:
    • Use lowercase letters in URLs.
    • Keep URLs descriptive and concise.
    • Avoid using special characters or spaces; use hyphens to separate words.
  7. Unique Title and Description: Avoid using duplicate title tags or meta descriptions across multiple pages.
  8. Sitemap and Robots.txt:
    • Sitemap: Create an XML sitemap that lists all the important pages of your website. This helps search engines understand the structure of your site.
    • Robots.txt: Use this file to instruct search engines on which pages or sections of the site should not be crawled or indexed.
  9. Mobile Responsiveness: Ensure your website is mobile-friendly. Google and other search engines prioritize mobile-optimized sites.
  10. Optimize Page Load Speed: Faster loading pages provide a better user experience and are favored by search engines.
  11. Use Canonical Tags: If you have duplicate content, use the canonical tag to tell search engines which version is the primary one.
  12. Internal Linking: Use internal links wisely to help users navigate your site and to spread page authority.
  13. Optimize Images: Compress images, use descriptive file names, and always include alt text for accessibility and SEO.
  14. Secure and Accessible Website: Ensure your website uses HTTPS and that your server returns the correct header response for each page.
  15. Structured Data: Implement schema markup where appropriate to provide search engines with more information about your content.
@niksmac
Copy link
Author

niksmac commented Sep 19, 2023

"Open Graph image" or "Twitter Card image" for social platforms is an important element for sharing content on social media. Here's a brief overview:

Meta Image (Open Graph Image & Twitter Card Image):

  1. Open Graph Image (for Facebook and most other social platforms):

    • Use the <meta property="og:image" content="URL_TO_IMAGE"> tag in the page's <head>.
    • Recommended size for the image is at least 1200 x 630 pixels for a good display on high-resolution devices.
    • The image should represent the content, be engaging, and of high quality.
  2. Twitter Card Image:

    • Use the <meta name="twitter:image" content="URL_TO_IMAGE"> tag.
    • While Twitter can use Open Graph tags, it's best to also include Twitter-specific tags if you want to ensure the content appears correctly on this platform.
    • Different card types (e.g., summary card, summary card with large image) have different image size recommendations. For the summary card with a large image, a 2:1 aspect ratio is recommended.

Including a relevant, high-quality meta image ensures that when your content is shared on social media, it's accompanied by a visual that can attract clicks and engagement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment