Generative Engine Optimization (GEO) Checklist.

F
  • 0/0 High Priority
  • 0/0 Medium Priority
  • 0/0 Low Priority
Generate Report
Filter by tags: All Crawling Tools Indexing Analytics Core Web Vitals Structure EEAT Keyword Research Content Optimization Blogs ECommerce Schema Landing Pages

Phase 1: Initial Setup and Foundation

0%
Phase 1: Initial Setup and Foundation items are

Ensure Site Crawling & Indexing

  1. Make sure your site can be crawled by search engines. Create an XML sitemap and submit it to Google Search Console and Bing Webmaster Tools. Verify that your important pages are not blocked by robots.txt or meta tags (use Search Console’s URL Inspection tool to check if pages are indexed). If AI tools can’t access your pages, they won’t show up in answers.
  • Crawling
  • Indexing

Use an SEO Plugin or Built-in Tools

  1. On platforms like WordPress, install a reputable SEO plugin (e.g. Yoast SEO, All in One SEO) to easily manage meta tags, sitemaps, and schema. On Shopify, Webflow, or others, utilize their SEO settings or apps for similar control. This will help you set titles, meta descriptions, and structured data without coding. (Example: adding schema markup helps search engines (including AI-driven ones) understand your content better, increasing chances to rank).
  • Tools

Enable Analytics & Tracking

  1. Set up Google Analytics 4 (GA4) for traffic monitoring and link it with Search Console. This lets you track overall traffic and see search query data. Also enable any platform-specific analytics (e.g. built-in stats on your CMS). Early on, establish a baseline so you can monitor improvement.
  • Analytics

Secure and Fast Website

  1. Use HTTPS (SSL) for your site – it’s table stakes for trust and rankings. Ensure your site loads quickly and is mobile-friendly, since slow or clunky sites hurt user experience and your chances of being cited in AI results. Use Google PageSpeed Insights to identify speed issues and a mobile-friendly test to confirm responsiveness. Basic improvements include optimizing images, enabling caching or a CDN, and using a lightweight theme.
  • Core Web Vitals

Organize a Clear Site Structure

  1. esign an intuitive navigation and URL structure. For example, group related content under logical categories. A clear hierarchy helps search bots (and AI) understand your site’s content. Each page URL should be readable (e.g. yoursite.com/blog/geo-checklist rather than a random string). Good structure also lays the foundation for internal linking in later phases.
  • Structure

Establish Trust Signals

  1. Set up essential pages like About Us, Contact, and Privacy Policy to show legitimacy. Include contact info or business addresses where relevant. These signals build credibility with users and AI. Ensure your content has an identifiable author with a bio if possible – it contributes to Experience/Expertise/Authority/Trust (E-E-A-T). For beginners, this might simply mean creating an “About the Author” blurb on blog posts or an author page.
  • EEAT

Tools & Resources

  1. Google Search Console, Bing Webmaster Tools, SEO Plugin (Yoast/AIOSEO for WordPress or SEO apps for Shopify/Webflow), Google Analytics 4, SSL certificate (via hosting), Google PageSpeed Insights, Mobile-Friendly Test.
  • Tools

Phase 2: Research and Planning for Generative Search

0%
Phase 2: Research and Planning for Generative Search items are

Keyword & Query Research with User Intent

  1. Expand beyond single keywords – think in terms of natural language questions and long-tail queries your audience might use. Use tools like Google Keyword Planner for base keywords and AnswerThePublic or AlsoAsked for common questions. Check Google’s “People Also Ask” box for question ideas. For example, a traditional keyword might be “healthy meal prep”, but an AI query could be “What can I cook for a quick healthy dinner when trying to lose weight?”. Identify these longer, conversational searches.
  • Keyword Research

Use AI for Search

  1. Try using ChatGPT, Google AI Mode, Gemini, Perplexity, Claude to brainstorm related questions. Prompt them with something like: “What questions do people have about [your topic]?” to uncover phrasing in a conversational style. These tools can suggest variations of questions that real users might ask, which you can then verify with search volume tools or intuition.
  • Keyword Research
  • Tools

Analyze the SERPs and AI Results

  1. Manually search your target questions in Google’s gemini, AI mode, ChatGPT, Claude, Perplexity, Grok to see what type of content gets summarized or cited. Note the sources that appear in AI-generated answers. For example, see if the AI summary pulls from forums, blogs, or product pages for those queries. This gives insight into content format and competitors.
  • Analytics

Topic Clustering and Content Calendar

  1. lan your content in clusters. Identify a broad “pillar” topic for a main page or article, and several supporting subtopics for detailed posts. By grouping related topics and linking them, you signal to AI that you have deep expertise in that area. For instance, if your site is about home brewing, a pillar could be “Home Brewing 101” with subtopics like “Equipment Guide”, “Common Beginner Mistakes”, “Home Brew Recipe: IPA”, etc. Map out a content calendar to cover these systematically.
  • Keyword Research
  • Content

Prioritize by Relevance and Feasibility

  1. You can’t cover every possible question, so prioritize. Focus on questions directly related to your niche/products (especially those with some traffic or frequently asked by customers). Also consider the difficulty – check if reputable sources already dominate an answer. Targeting specific, under-served questions can be a quick win in AI results. For example, a very niche question with little existing content might let you become the go-to source that AI cites.
  • Content

Understand User Intent

  1. For each topic, clarify the intent – are users looking for a how-to, a definition, a comparison, etc.? Plan to meet that intent thoroughly. If someone asks “How do I fix X?”, they expect step-by-step instructions (perhaps with a HowTo schema). If they ask for a definition, prepare a concise definition at the top of your content. Aligning content format to intent makes it more likely AI will use your content to answer that query.
  • Keyword Research
  • Content

Plan Content Types Accordingly

  1. Decide which format suits each topic: blog post for informational/how-to queries, product page for commercial queries, landing page for service info, or multimedia if it’s demonstration-based. For example, a “how to” query might do well as a blog article with text and images, whereas “Product X vs Product Y” might be a comparison landing page or blog post with a table. We’ll cover specific optimization for each content type in the next phase.
  • Keyword Research
  • Content

Tools & Resources (Phase 2)

  1. Google Keyword Planner (for base keywords), AnswerThePublic / AlsoAsked (for questions), ChatGPT or Bard (for query brainstorming), Reddit/Quora (search these forums for real user questions in your niche), Google Trends (to compare interest in topics), any SEO tool like Semrush/Ahrefs (for keyword difficulty and related questions).
  • Tools

Phase 3: Content Creation & Optimization for Blog Posts (Articles)

0%
Phase 3: Content Creation & Optimization for Blog Posts (Articles) items are

Use Descriptive, Question-Focused Titles

  1. Craft a clear title (H1) that includes the question or topic the post addresses in natural language. For example, “How to Brew Kombucha at Home – Step-by-Step Guide” rather than a vague title. This signals relevance to AI and humans alike about the question being answered.
  • Content
  • Optimization
  • Blogs

Lead with a Quick Answer or Summary

  1. In the opening paragraph, provide a concise answer or definition of the main query in 1–3 sentences. Assume an AI or snippet feature might quote this directly. For instance: “What is GEO? Generative Engine Optimization (GEO) is the practice of optimizing your content so AI-powered search engines include it in their answers.” Front-loading the answer helps both readers and AI.
  • Content
  • Optimization
  • Blogs

Write in Short, Clear Sections

  1. Break the content into modular sections of about 2–4 short paragraphs each, focused on subtopics or sub-questions
  2. . Each section should ideally answer a single question or aspect of the topic in 100-300 words. AI engines often pull information in chunks, so ensure each section can stand alone in value. Use subheadings (H2s/H3s) phrased as questions where appropriate (e.g., “How Does GEO Differ from SEO?”) to mirror user queries.
  4. Keep Paragraphs and Sentences Concise: Aim for paragraphs of 2-5 sentences and sentences
  • Content
  • Optimization
  • Blogs

Keep Paragraphs and Sentences Concise

  1. Aim for paragraphs of 2-5 sentences and sentences under ~20 words
  2. . Dense walls of text or long run-ons can confuse AI models. One idea per paragraph is a good rule. This writing style not only helps AI parse your content, but also improves human readability.
  • Content
  • Optimization
  • Blogs

Use Bullet Points, Steps, and Formatting

  1. Where possible, use lists or steps to break out key points (like we’re doing here!). Structured formats (bulleted lists, numbered steps, tables) are easier for AI to extract and present. For example, if explaining a process, list the steps 1-2-3. Bold important terms or conclusions so they stand out – this highlights key information for skimmers and possibly for AI summarization.
  • Content
  • Optimization
  • Blogs

Include an FAQ Section

  1. Add a brief FAQ at the end of the post (or scattered as drop-down questions in the content) tackling common follow-up questions. For instance, after an article on brewing kombucha, FAQs could be “How long does homemade kombucha last?” or “Can I flavor kombucha during fermentation?”. Write each answer in 2-4 sentences, in a straightforward tone (and consider marking them up with FAQ schema – more on schema in Phase 4). Visible Q&A content can directly feed AI answers.
  • Content
  • Optimization
  • Blogs

Provide Evidence and Data

  1. Wherever relevant, include specific facts, statistics, or quotes from experts. AI models are more likely to cite content that contains concrete data or memorable, quotable lines. For example: “According to a 2023 study, email marketing yields an ROI of $42 per $1 spent.” Such specifics enhance your E-E-A-T and make your content “citation-ready”. (Always cite your sources for these stats – linking to authoritative sources also boosts credibility.)
  • Content
  • Optimization
  • Blogs

Demonstrate E-E-A-T

  1. Write with a confident, knowledgeable tone. Share first-hand experience or insights if you have them (e.g., “In my 5 years of brewing kombucha, I found…”). Link to authoritative references to back up claims. Include an author byline with a short bio highlighting expertise or experience in the topic (e.g., “Jane Doe, Fermentation Enthusiast”). These practices build Expertise, Authoritativeness, and Trustworthiness, which make AI more likely to view your content as reliable.
  • Content
  • Optimization
  • Blogs

Internal Linking

  1. Within the blog post, link important terms or related questions to your other relevant posts (or sections of a pillar page). For example, if you mention “fermentation temperature,” link it to another article that covers that in depth. This reinforces topical connections for AI and helps it see you cover the subject comprehensively. It also keeps readers engaged on your site.
  • Content
  • Optimization
  • Blogs

Use AI Content Tools Wisely

  1. You can use generative tools like ChatGPT to help draft sections or brainstorm examples, but always edit thoroughly. Ensure the final content is accurate, original in voice, and adds real value (AI outputs can be generic). Tools like Grammarly or Hemingway Editor are helpful to polish grammar and simplify language, ensuring clarity. Always fact-check AI-provided content against reliable sources to avoid misinformation.
  • Content
  • Optimization
  • Blogs

Phase 4: Content Creation & Optimization for Product Pages (E-commerce or Service Product pages)

0%
Phase 4: Content Creation & Optimization for Product Pages (E-commerce or Service Product pages) items are

Clear Product Description Up Top

  1. Start with a concise summary of what the product or service is and who it’s for, in plain language. Think of it as an elevator pitch: the first 1-2 sentences should define the product clearly (e.g., “WidgetPro is a compact kitchen gadget that chops and mixes vegetables automatically, ideal for busy home cooks.”). This helps if an AI is asked “What is WidgetPro?” – your page provides a ready answer.
  • Content
  • Optimization
  • ECommerce

Comprehensive Details and Specifications

  1. Don’t skimp on details. Provide all the info a user or AI might look for: features, specifications, dimensions, ingredients/materials, usage instructions, pricing, etc. Use bullet points or a specs table for clarity. For example, list key features as bullets (“Auto-shutoff after 5 minutes”, “Dishwasher-safe parts”, etc.). A generative AI might pull these feature points if someone asks “What are the features of WidgetPro?”.
  • Content
  • Optimization
  • ECommerce

Optimize with Product Schema

  1. Implement Product structured data (JSON-LD or via your platform’s plugin) to mark up name, description, price, availability, and reviews. This markup helps search engines and AI understand the content as a product. Many e-commerce platforms do this by default or have apps for it. If using WooCommerce or Shopify, ensure your product SEO fields (like price, SKU, etc.) are filled out – they often auto-generate schema. This can enhance how your product appears in search and possibly AI results.
  • Content
  • Optimization
  • ECommerce
  • Schema

Include High-Quality Images (with Alt Text)

  1. Show multiple images of the product and add descriptive alt text for each (e.g., “Alt: WidgetPro kitchen gadget chopping carrots”). Alt text not only aids accessibility but also describes the image content to AI. If an AI result includes image analysis, a good alt text can be valuable. For any infographic or chart about the product (like a size chart or performance graph), describe it in the text or caption so AI can capture that info.
  • Content
  • Optimization
  • ECommerce

Address Common Questions on the Page

  1. Add a small FAQ or Q&A section on the product page addressing frequent customer questions: “Does this come with a warranty?”, “How does this compare to [Competitor]?”, “What is the return policy for WidgetPro?” etc. Answer in a straightforward manner. Not only does this help customers directly, but if someone asks an AI “Does WidgetPro have a warranty?”, your site may be cited if it contains that Q&A. Remember to also include these questions/answers in FAQ schema for maximum visibility.
  • Content
  • Optimization
  • ECommerce

Social Proof and Reviews

  1. Include user reviews, ratings, or testimonials on the product page if possible. This user-generated content can contain natural language descriptions and use-cases that AI might latch onto (and it boosts trust for human visitors). Mark up reviews with Review schema if applicable. For instance, if someone asks “Is WidgetPro reliable?”, an AI might reference a statement from a review on your site if it’s relevant.
  • Content
  • Optimization
  • ECommerce

Comparison and Alternative Mentions

  1. If appropriate, mention competitor products or alternative solutions by name (in a fair context). Generative AI often answers comparative queries and might cite sources that discuss multiple options. If your product page politely compares WidgetPro to other products (“WidgetPro vs CompetitorX”), you increase chances of appearing when someone asks “WidgetPro vs CompetitorX – which is better?”. Co-citations of your brand alongside others signal to AI the competitive landscape. Just ensure any comparisons are accurate and not overly biased.
  • Content
  • Optimization
  • ECommerce

Technical Info for Troubleshooting

  1. If relevant, include a section for troubleshooting or technical details (FAQs like “What to do if it stops working?” or a link to a support page). AI assistants might use this if someone asks something like “How to fix issue X with WidgetPro.” Being the source of a helpful answer can drive people to click through for more.
  • Content
  • Optimization
  • ECommerce

Performance & Mobile Optimization

  1. Product pages must load fast and work well on mobile, as shoppers (and search crawlers) expect speed. Compress images (use modern formats like WebP if supported), and consider lazy-loading below-the-fold images. Use tools like GTmetrix to analyze page load. Mobile-first is key especially if voice search or AI on mobile is used by shoppers
  2. (e.g., via Siri or Google Assistant). A fast, clean page is more likely to be favored by search algorithms, which indirectly helps GEO.
  • Content
  • Optimization
  • ECommerce

Calls to Action & Conversion

  1. While not directly about AI, ensure your product page has clear calls to action (Add to Cart, Contact Us, etc.). If an AI search does bring a user to your page, you want them to easily take the next step. A/B test different page layouts or wording if needed (e.g., test if a trust badge or a different CTA text increases clicks). Even simple changes like the placement of an “Buy Now” button can be tested – many CMS platforms have A/B testing plugins or you can use tools like Google Optimize (note: it was discontinued in 2023, but alternatives like Optimizely or VWO exist).
  • Content
  • Optimization
  • ECommerce

Phase 5: Content Creation & Optimization for Landing Pages (Service Pages or Homepage)

0%
Phase 5: Content Creation & Optimization for Landing Pages (Service Pages or Homepage) items are

Clearly State Your Value Proposition

  1. At the top of the page, have a clear heading and a short paragraph that describes what you offer or what the page is about. For a homepage, this is your slogan or mission; for a service page, it’s the summary of that service. Make it specific and jargon-free. For example: “Professional Roofing Services in Dallas – Trusted Repairs & Installations for 20+ Years.” This immediate clarity helps AI understand your business offering and might be quoted for queries like “What does [Company] do?”
  • Content
  • Optimization
  • Landing Pages

Use Headings as Signposts

  1. Break the page into sections with descriptive headings. Common sections might include “How It Works,” “Services We Offer,” “Why Choose Us,” “Testimonials,” etc. Each section’s content should directly follow from its heading. For instance, under “How It Works,” immediately explain the process in a stepwise manner. Logical, well-labeled sections make it easier for AI (and users) to navigate your content. If a user asks “how does [Your Service] work?”, an AI might pull from that specific section.
  • Content
  • Optimization
  • Landing Pages

Concise, Benefit-Driven Content

  1. Write short paragraphs focusing on benefits and key points. Avoid filler or overly promotional language. Generative AI prefers factual, useful content over marketing fluff. Highlight features or benefits in bullet lists if possible (e.g., a bulleted list of “What you get” or “Key Benefits”). This structured approach can be parsed by AI – if someone asks “What are the benefits of [Service]?”, your bullets could be the source of the answer.
  • Content
  • Optimization
  • Landing Pages

Incorporate FAQs for Services

  1. Just like with blog and product pages, include an FAQ section on service pages or the homepage if relevant. Think of questions prospective customers often ask about your service or company: “How do consultations work?”, “Do you offer a guarantee?”, “What areas do you serve?”, etc. Provide straightforward answers. These not only help site visitors but also position your content for voice search and AI assistants (e.g., “Does [Company] offer free estimates?” could trigger your FAQ content). Mark these up with FAQ schema when possible.
  • Content
  • Optimization
  • Landing Pages

Multimedia and Testimonials

  1. Enrich the page with multimedia that adds value – e.g., an explainer video, a customer testimonial video, or before-and-after images. AI can’t “see” videos or images directly, but caption them or describe them in text. For example, include a caption like “Client Testimonial: ‘[Company] fixed our roof in 2 days…’” or text highlights from a video. This way, even if users don’t watch the video, the key points are available for AI to consume. Testimonials and case studies build trust (human and AI likely give weight to evidence of satisfaction).
  • Content
  • Optimization
  • Landing Pages

Local and Schema Markup

  1. If your landing page is location or service-specific, use LocalBusiness schema or relevant schema to mark up your business name, address, phone, and services. Also ensure those details are visible on the page (in text) for AI to pick up. For instance, if someone asks “Is there a roofing company in Dallas that offers solar panel installation?”, having that text on your page (and perhaps marked in schema) increases your chances. Embed Google Maps or mention your service areas in text for local relevance.
  • Content
  • Optimization
  • Landing Pages
  • Schema

Fast, User-Friendly Design

  1. Keep the page design clean and ensure it loads quickly. Minimize heavy scripts or interstitials that delay content. Remember, if your page content “loads in” via complex scripts after a second or two, an AI crawler might miss it
  2. . Prefer server-side rendering for content (or use prerendering services if you have a single-page app). The content should be present in the initial HTML. Beginners using standard CMS templates usually are fine here, but avoid too much dynamic content that isn’t in the source.
  • Content
  • Optimization
  • Landing Pages

Call-to-Action and Conversion Goals

  1. Make your CTA obvious (e.g., “Contact us for a free quote” button). From a GEO perspective, a user might not even click through if the AI provides the answer – but when they do click your landing page, guide them to the next step. Track these conversions with Google Analytics or other tools. Over time, you can experiment (A/B test) with different headlines or layouts to see what keeps users (and possibly AI) engaged. For example, test an alternative headline that explicitly answers a common question and see if time-on-page or conversion rate improves.
  • Content
  • Optimization
  • Landing Pages

Phase 6: Content Creation & Optimization for Multimedia Content (Videos, Podcasts, Images)

0%
Phase 6: Content Creation & Optimization for Multimedia Content (Videos, Podcasts, Images) items are

Provide Text Transcripts or Summaries

  1. For any video or podcast you produce, always include a transcript or at least a detailed summary on the same page. This is crucial – AI systems primarily consume text. For example, if you have a 10-minute explainer video, write a summary of the key points or a full transcript below the video.This way, if someone asks a question that your video answers, the AI can find the answer in the text. Tip: YouTube auto-generates captions for videos; you can download and refine those to create a transcript.
  • Content
  • Optimization

Use Descriptive Titles and Metadata

  1. Give your videos and podcasts clear titles and descriptions. Instead of “Episode 5 – Audio”, title it “Podcast Episode 5: How to Improve Website Speed”. The description field (on YouTube, Vimeo, your podcast host, etc.) should be filled out with a summary and keywords. These often feed search engines. If an AI is leveraging YouTube data, a good description helps it understand the video content.
  • Content
  • Optimization

Alt Text for Images and Infographics

  1. Treat images as content, not decoration. Any image that conveys important info (like an infographic, chart, or example) should have descriptive alt text or an accompanying description. For instance: alt="Line graph showing website traffic increase after SEO changes (traffic doubled from Jan to June)". This way, if an AI is summarizing your page, it can include the insight from the image (e.g., “traffic doubled from Jan to June”) because you provided it in text.
  • Content
  • Optimization

Captions and Surrounding Text

  1. Use captions under images or timestamp highlights for videos. Captions not only explain images for users but are also indexed. For a video, you might list key takeaways or timestamps (e.g., “[00:00 – 01:00] Introduction to GEO definition; [01:00 – 02:30] Three principles of GEO…”). This structured breakdown can be useful for AI and helps users navigate content too.
  • Content
  • Optimization

Schema Markup for Media

  1. Where applicable, use VideoObject schema for videos (it can include transcript, duration, upload date, etc.) and AudioObject/Podcast schema for audio content. If you embed YouTube videos on your site, Google often automatically detects info, but adding schema can help ensure AI knows there’s a video and what it’s about. Similarly, an infographic might be annotated with ImageObject schema. These may indirectly help your content appear in relevant searches (e.g., showing a video thumbnail in results, or being referenced by an AI when a tutorial is asked).
  • Content
  • Optimization
  • Schema

Host on Accessible Platforms

  1. Host videos on platforms that are crawlable (YouTube is a good choice as Google/AI can parse it to some extent, and YouTube’s transcription/caption system feeds Google’s understanding). If using a custom video player, ensure it’s not blocking crawlers. For podcasts, provide a web player or download link along with show notes so that content is accessible.
  • Content
  • Optimization

Encourage Engagement Signals

  1. While not directly an AI optimization, encourage users to share or comment on your multimedia (e.g., embed YouTube comments or allow comments on your blog). High engagement (views, likes, shares) on YouTube or similar platforms can be a proxy for quality – while AI might not “see” the likes, popular content is more likely to surface in searches that AI tools pull from. For instance, Perplexity or Bing might favor citing a well-viewed YouTube video’s info (via its transcript) over an obscure one.
  • Content
  • Optimization

Optimize File Names and Sizes

  1. Name your media files descriptively (e.g., how-to-tie-a-knot-video.mp4 instead of VID1234.mp4). This is minor, but every bit of context can help. Also, compress media for faster loading – slow-loading media can hurt page performance. Videos can be lazy-loaded or hosted on a fast CDN. Remember, user experience factors like speed can indirectly affect SEO and thus GEO.
  • Content
  • Optimization

Use Multimedia to Enhance (not replace) Content

  1. Multimedia should supplement your text content, not stand alone. For example, if you have a video tutorial on a blog post, also write out the main steps in text. A generative AI might present a user with a summary that “there’s a great video on this page,” but unless the user clicks, that alone doesn’t help you. By providing the content in text as well, you ensure the AI can directly use your material in its answer, increasing the likelihood of a user clicking through for full context or additional info. Remember: AI “extracts” content; the more extractable (textual and structured) you make your media’s message, the more value it can provide
  • Content
  • Optimization

Tools & Resources

  1. Content Writing: ChatGPT / Google Bard (for drafting text or generating ideas), Grammarly (for proofreading), Hemingway Editor (for simplifying text).
  3. Multimedia: YouTube (for hosting videos and auto-transcripts), Descript or Otter.ai (for transcribing audio/video), Canva (to create infographics with clear text), image compression tools (TinyPNG, Squoosh), schema generators (Google’s Structured Data Markup Helper or plugins that support schema for FAQ, video, etc.).
  5. General: Your CMS’s editing tools (make use of heading styles, list formats, etc.), and SEO plugins which often check readability and content length (Yoast’s readability analysis, for example, can flag long paragraphs or passive voice).
  • Tools

Phase 7: On-Page SEO and Technical Optimization

0%
Phase 7: On-Page SEO and Technical Optimization items are

Craft Unique Titles & Meta Descriptions

  1. Make sure every page has a unique, descriptive tag (the page title that appears in search results) that clearly reflects the content. Keep it natural and use words someone would actually search for. For example: “How to Optimize Your Site for AI Search (Generative Engine Optimization Guide)”. Write a meta description that summarizes the page in one or two enticing sentences (even though AI may not use it directly, it helps click-through on regular SERPs). These meta tags help both users and AI quickly grasp your page’s topic.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Use Proper Heading Hierarchy</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Check that your pages have one H1 (the main title) and logical H2, H3 subheadings following a hierarchy. This semantic structure is important for AI parsing. As noted earlier, phrasing some headings as questions or clear descriptors is beneficial. Under each heading, the content should directly answer or discuss that heading’s topic – this tight coupling helps AI understand context. Avoid cute or clever headings that are too vague; clarity is key.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="structure">Structure</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Implement Structured Data (Schema Markup)</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >This is a critical step for GEO. Add relevant schema to your pages to give search engines explicit context about your content. Prioritize: FAQPage schema for pages with FAQs, HowTo schema for instructional content, Article/BlogPosting schema for blog posts, Product schema for product pages, VideoObject for video content, etc. Structured data is like a cheat sheet for AI, making it easier for them to identify questions, answers, steps, products, and more. For beginners, the easiest route is using tools: many SEO plugins will let you add FAQ or HowTo schema by simply filling out forms. Alternatively, use an online schema generator (there are free ones where you input Q&A and it gives JSON-LD code). Always test your structured data using Google’s Rich Results Test tool to ensure there are no errors before deploying.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="schema">Schema</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Ensure Content is Crawlable & Renderable</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Some website builders load content dynamically via JavaScript (for example, content appears only after user interaction or after scripts run). Check if your main content is present in the raw HTML. You can use Google’s URL Inspection (in Search Console) or the Rich Results Test to see how Googlebot views your page. If you see that important text is missing, you may need to implement server-side rendering or use simpler coding approaches so that crawlers (and AI) can “see” everything. In short: content that loads only after a delay or requires logins will not be included in AI answers. Aim for all essential info to load immediately and publicly.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="crawling">Crawling</li> <li class="list-tag" data-tag="indexing">Indexing</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Optimize Site Speed and Core Web Vitals</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Fast sites provide a better user experience and indirectly help your SEO/GEO. Google’s algorithms consider Core Web Vitals (loading speed, interactivity, layout stability). AI search might not explicitly favor faster sites, but users certainly do, and Google’s indexation might. Use Google Lighthouse (built into Chrome DevTools) or PageSpeed Insights to get performance diagnostics. Address high-impact issues: enable compression, minify CSS/JS, use browser caching, and consider a CDN. On WordPress, caching plugins (WP Rocket, W3 Total Cache) can help; on other CMS, see if they have performance settings or use Cloudflare for CDN/caching. Remember mobile performance too – many searches (including voice queries) happen on mobile devices</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="core web vitals">Core Web Vitals</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Mobile-Friendly and Responsive Design</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Ensure your site is mobile-responsive. Test pages on a phone or using your browser’s device emulator. Buttons/tap targets should be easy to click, text readable without zooming. Google predominantly uses mobile-first indexing, and voice assistants (Siri, Google Assistant) draw answers from mobile-friendly content. A page that is unusable on mobile may not surface as often. Use Google’s Mobile-Friendly Test to spot issues.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="core web vitals">Core Web Vitals</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Link Relevant Content (Internal Links)</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Go through your pages and ensure you’re linking to other relevant pages on your site where it makes sense. For example, a blog post mentioning your product should link to the product page; a service page discussing a topic in depth could link to a detailed blog post on that topic. These internal links create a web of context that AI can follow, reinforcing how your content pieces relate. They also keep users engaged. Use descriptive anchor text (e.g., “learn how GEO differs from SEO” rather than “click here”) – this adds semantic value.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="content">Content</li> <li class="list-tag" data-tag="optimization">Optimization</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--red"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Fix Technical SEO Issues</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Run an SEO audit (many SEO plugins have audit features, or use free tools like SEO Site Checkup or Neil Patel’s SEO Analyzer) to catch technical issues: broken links, missing alt tags, duplicate meta tags, etc. For a larger site, you could use Screaming Frog SEO Spider (free up to 500 URLs) to crawl and find problems. Broken links or missing tags won’t directly stop AI from reading your content, but they degrade overall site quality. Particularly ensure every image has alt text (especially ones with informative graphics) and that 404 errors are minimized.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--yellow"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Use Analytics & Console for On-Page clues</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >In Search Console’s performance reports, look at queries your pages appear for. Are your title and description compelling users to click? A low click-through rate might mean you need to tweak the meta title/description to better match the query intent. Also check the Index Coverage and Page Experience (Core Web Vitals) reports – fix any errors or warnings. These tools ensure your on-page SEO is solid, which in turn supports GEO efforts (since a page not indexed or considered poor quality won’t be used by AI).</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="optimization">Optimization</li> <li class="list-tag" data-tag="core web vitals">Core Web Vitals</li> <li class="list-tag" data-tag="analytics">Analytics</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--yellow"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Highlight Key Terms and Define Them</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >If your page uses any important terms or jargon, consider briefly defining them (or use a glossary tooltip plugin). AI models appreciate when content includes definitions or explanations of complex terms, sometimes even preferring content that says “Definition: …” for certain queries. You might incorporate a small “Key Point” or “Definition” callout box in your content. For example: Definition: GEO (Generative Engine Optimization) is optimizing content for AI-driven search results. This not only helps newbies but also signals AI exactly how to quote the definition if needed.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="content">Content</li> <li class="list-tag" data-tag="optimization">Optimization</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--yellow"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Quality Assurance – Human Touch</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >Finally, read through your pages as if you were a user. Is it easy to find answers on the page? Does the writing flow well and sound human (not stuffed with keywords)? AI prefers content that has a natural, human-like flow, as it indicates quality. Eliminate any redundant or filler content. Ensure your tone is consistent and approachable. You want the content to be engaging for readers, because user engagement metrics (time on page, bounce rate) could indirectly influence how search engines perceive your content’s value.</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="content">Content</li> <li class="list-tag" data-tag="optimization">Optimization</li> </ul> </div> <div class="checklist__section-item js-checklist-item accessibility-item "> <div class="checklist__section-item-head"> <div class="checklist__section-item-label"> <div class="priority priority--green"></div> <div class="checklist__section-item-label-inner js-checklist-checkbox" data-block="accessibility"> <div class="checkbox"></div> <h3 class="name"> <span class="description">Tools & Resources</span> </h3> </div> </div> <div class="checklist__section-item-btn js-checklist-btn"></div> </div> <div class="checklist__section-item-body js-checklist-drop"> <div class="checklist__section-github"> <ol> <li><span style="color: #EF572C;" >SEO Audit: Google Search Console (Coverage, Page Experience reports), Screaming Frog (crawl for issues), SEO plugin’s site analysis (if available), Site audit tools (Semrush, Ahrefs site audit if you have access). </span></li> <li><span style="color: #EF572C;" >Structured Data: Google Rich Results Test (validate schema), Schema.org documentation (for reference), CMS plugins or generators for schema (Yoast structured data blocks, AIOSEO schema generator, etc.). </span></li> <li><span style="color: #EF572C;" >Performance: Lighthouse in Chrome (audit performance/accessibility), PageSpeed Insights, GTmetrix (detailed waterfall analysis), Cloudflare or other CDN for speed, caching plugins, image optimizers. </span></li> <li><span style="color: #EF572C;" >Mobile-Friendly: Google Mobile-Friendly Test, Browser dev tools device mode. </span></li> <li><span style="color: #EF572C;" >General: Grammar and spell checkers (quality content is error-free), and possibly accessibility checkers (accessibility often aligns with machine-readable clarity).</span></li> </ol> </div> </div> <ul class="checklist__section-item-tags"> <li class="list-tag" data-tag="tools">Tools</li> </ul> </div> </div> </div> </section> </div> </div> </div> <script> $(document).ready(function() { var total_red = $('.priority--red').length; var total_yellow = $('.priority--yellow').length; var total_green = $('.priority--green').length; $('#total-red').text(total_red); $('#total-yellow').text(total_yellow); $('#total-green').text(total_green); $(document).on('click', '.js-checklist-checkbox, .js-checklist-checked-all, .js-checklist-unchecked-all', function() { var block = $(this).attr('data-block'); var current_red = $('.checked').find('.priority--red').length; var current_yellow = $('.checked').find('.priority--yellow').length; var current_green = $('.checked').find('.priority--green').length; $('#current-red').text(current_red); $('#current-yellow').text(current_yellow); $('#current-green').text(current_green); var items = document.querySelectorAll('[data-block="' + block + '"]'); var items_length = items.length - 2; var current_items = $('.' + block + '-item'); current_length = 0; $(current_items).each(function() { if($(this).hasClass('checked')) { current_length = Number(current_length) + Number(1); } }); var total = current_length / items_length * 100; $('.' + block + '-progressbar').find('.progress').css({'width': total.toFixed(2) + '%'}); $('.' + block + '-progressbar').find('.value').text(total.toFixed(2) + '%'); }) $(document).on('click', '.checklist__tags-link', function(e) { e.preventDefault(); $('.checklist__tags-link').removeClass('active'); $(this).addClass('active'); var tag = $(this).attr('data-tag'); var tags = $('.list-tag');console.log(tags); if(tag == 'all') { $('.js-checklist-item').show(); } else { var i = 0; $(tags).each(function() { var current_tag = $(this).attr('data-tag'); if(i == 0) { if(tag == current_tag) { $(this).closest('.js-checklist-item').show(); i++; console.log(i); } else { $(this).closest('.js-checklist-item').hide(); console.log(i); } } }); } }) $(document).on('click', '.save-checklist', function(e) { e.preventDefault(); var project_name = $('.project_name').val(); var project_url = $('.project_url').val(); var dev_name = $('.dev_name').val(); var user_id = $(this).attr('data-user_id'); var id = $(this).attr('data-id'); var title = $('.checklist-title').val(); var slug = $('.checklist-slug').val(); if(project_name.length > 0) { $('.project-name-error').hide(); } else { $('.project-name-error').show(); $('.project-name-error').text('Project Name is required field!'); } if(project_url.length > 0) { $('.project-url-error').hide(); } else { $('.project-url-error').show(); $('.project-url-error').text('Project Url is required field!'); } if(dev_name.length > 0) { $('.dev-name-error').hide(); } else { $('.dev-name-error').show(); $('.dev-name-error').text('Developer Name is required field!'); } if(project_name.length > 0 && project_url.length > 0 && dev_name.length > 0) { var red = $('#current-red').text() + '/' + $('#total-red').text(); var yellow = $('#current-yellow').text() + '/' + $('#total-yellow').text(); var green = $('#current-green').text() + '/' + $('#total-green').text(); var head = []; var html = []; var webfonts = []; var css = []; var javascript = []; var images = []; var accessibility = []; var performance = []; var seo = []; getCheckedBlocks('#head-block', '.head-item', head); getCheckedBlocks('#html-block', '.html-item', html); getCheckedBlocks('#webfonts-block', '.webfonts-item', webfonts); getCheckedBlocks('#css-block', '.css-item', css); getCheckedBlocks('#javascript-block', '.javascript-item', javascript); getCheckedBlocks('#images-block', '.images-item', images); getCheckedBlocks('#accessibility-block', '.accessibility-item', accessibility); getCheckedBlocks('#performance-block', '.performance-item', performance); getCheckedBlocks('#seo-block', '.seo-item', seo); var data = {'project_name': project_name, 'project_url': project_url, 'dev_name': dev_name, 'user_id': user_id, 'head': head, 'html': html, 'webfonts': webfonts, 'css': css, 'javascript': javascript, 'images': images, 'accessibility': accessibility, 'performance' : performance, 'seo': seo, 'red': red, 'yellow' : yellow, 'green': green, 'title': title, 'slug': slug, 'id': id}; $.ajax({ url: '/theme/nts/ajax/save-checklist.php', type: 'post', dataType: 'json', data: data, success: function(response) { $('.save-button').text('Saved!'); $('.project_name').val(response.project_name); $('.project_url').val(response.project_url); $('.dev_name').val(response.dev_name); $('.project_name_span').text(response.project_name); $('.project_url_span').text(response.project_url); $('.dev_name_span').text(response.dev_name); $('.edit').attr('data-id', response.last_id); setTimeout(function() { $('.save-button').text('Save Checklist'); }, 3000) $('.project_name').hide(); $('.project_url').hide(); $('.dev_name').hide(); $('.error-message').hide(); $('.checklist-span').show(); $('.edit').text('Edit Checklist'); $('.edit').addClass('edit-checklist'); $('.edit').removeClass('save-checklist'); } }); } else { $('html,body').stop().animate({ scrollTop: $('#checklist').offset().top }, 700); } }) $(document).on('click', '.edit-checklist', function(e) { e.preventDefault(); $('.project_name').show(); $('.project_url').show(); $('.dev_name').show(); $('.error-message').show(); $('.checklist-span').hide(); $(this).text('Save Checklist'); $(this).addClass('save-checklist'); $(this).removeClass('edit-checklist'); }) }) function getCheckedBlocks(block, item, el) { var arr = $(block).find(item); arr.each(function(index) { if($(this).hasClass('checked')) { el.push(index); } }); return el; } </script> <footer class="footer"> <div class="container-fluid"> <div class="subscription"> <div class="container container-mod"> <div class="subscription__wrapper"> <div class="text-wrapper"> <div class="subscription-header">Subscribe to Kwebby<span class="colored-dot">.</span></div> <div class="subscription-text">Get the latest posts delivered right to your email.</div> </div> <div class="email-wrapper"> <form> <div class="form-group"> <input type="text" class="email-subscribe" placeholder="Enter your Email address"> <span class="error-message" style="display: none; color: white;">This text is required.</span> <span class="success-message" style="display: none; color: white;"></span> <button type="submit" class="send-email"> Subscribe </button> </div> </form> <p class="msg_subscribe"></p> </div> </div> </div> </div> <div class="footer__wrapper"> <div class="container"> <div class="footer__logo"> <a href="https://kwebby.com/"> <img src="https://kwebby.com/theme/nts/images/logo-white.svg" width="144px" height="34px" alt="k"> </a> </div> <div class="footer__socials"> <ul> <li> <a href="https://www.facebook.com/kwebbydigital/" target="_blank"> <svg class="icon facebook"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#facebook"></use> </svg> </a> </li> <li> <a href="#"> <svg class="icon twitter"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#twitter"></use> </svg> </a> </li> <li> <a href="https://instagram.com/kwebby.digital" target="_blank"> <svg class="icon instagram"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#instagram"></use> </svg> </a> </li> <li> <a href="https://kwebby.com/contact" target="_blank"> <svg class="icon envelop"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#envelop"></use> </svg> </a> </li> <li> <a href="https://youtube.com/@kwebby" target="_blank"> <svg xmlns="http://www.w3.org/2000/svg" width="18" height="14" viewBox="0 0 18 14" fill="none"> <path d="M9 14C1.59 14 0 13.3969 0 7C0 0.603077 1.59 0 9 0C16.41 0 18 0.603077 18 7C18 13.3969 16.41 14 9 14ZM9 1.07692C1.78744 1.07692 1.125 1.57518 1.125 7C1.125 12.4248 1.78744 12.9231 9 12.9231C16.2126 12.9231 16.875 12.4248 16.875 7C16.875 1.57518 16.2126 1.07692 9 1.07692ZM7.3125 10.7692C7.22156 10.7692 7.13006 10.7482 7.04719 10.7057C6.86419 10.6118 6.75 10.4293 6.75 10.2308V3.76923C6.75 3.57072 6.86419 3.38818 7.04719 3.29431C7.22925 3.20044 7.45125 3.21067 7.6245 3.32105L12.687 6.55182C12.8436 6.65197 12.9375 6.81997 12.9375 7C12.9375 7.18003 12.8436 7.34803 12.687 7.448L7.6245 10.6788C7.53038 10.7387 7.42163 10.7692 7.3125 10.7692ZM7.875 4.77544V9.22456L11.361 7L7.875 4.77544Z"/> </svg> </a> </li> </ul> </div> <div class="footer__menu"> <ul> <li> <a href="https://kwebby.com/">Home</a> </li> <li> <a href="https://kwebby.com/contact">Contact</a> </li> <li> <a href="https://kwebby.com/blog/about-us">About Us</a> </li> <li> <a href="https://kwebby.com/blog/whats-new">What’s New</a> </li> <li> <a href="https://kwebby.com/blog/terms-conditions">Terms & Conditions</a> </li> <li> <a href="https://kwebby.com/blog/privacy-policy">Privacy Policy</a> </li> <li> <a href="https://kwebby.com/blog/advertisers">Advertisers</a> </li> </ul> </div> <div class="copyrights"> <span>Copyright © 2018-24 Kwebby Pvt Ltd. All rights reserved.</span> </div> </div> </div> <!-- <div class="chat-icon"> <a href="javascript:void(0)"> <img src="https://kwebby.com/theme/nts/images/chat-icon.png" alt="chat-icon"> </a> </div> --> </div> <!-- Modals --> <div class="modal js-modal js-modal-login" id="signin" role="dialog"> <div class="popup__wrap"> <div class="modal__wrapper"> <div class="modal__form"> <h3 class="left-side-h3">Login</h3> <div class="top-section__title">Sign in using social network</div> <form method="POST" action="https://kwebby.com/account/login" class="loginme-form"> <div class="modal__socials social"> <div class="social-content"> <!--<a href="https://kwebby.com/facebook/login" class="social-btn social-btn--facebook" title="Sign in using Facebook">--> <!-- <span class="social-btn-icon">--> <!-- <img src="https://kwebby.com/theme/nts/images/facebook-white.svg" alt="">--> <!-- </span>--> <!-- <span class="social-btn-txt">Facebook</span>--> <!--</a>--> <a href="https://kwebby.com/google/login" class="social-btn social-btn--mail" title="Sign in using Google"> <span class="social-btn-icon"> <img src="https://kwebby.com/theme/nts/images/google-white.svg" alt=""> </span> <span class="social-btn-txt">Google</span> </a> <!--<a href="https://kwebby.com/twitter/login" class="social-btn social-btn--twitter" title="Sign in using Twitter">--> <!-- <span class="social-btn-icon">--> <!-- <img src="https://kwebby.com/theme/nts/images/twitter-white.svg" alt="">--> <!-- </span>--> <!-- <span class="social-btn-txt">Twitter</span> --> <!--</a>--> </div> </div> <div class="top-section__title">Sign in with your username</div> <div class="form-group"> <label class="text">Username</label> <div class="form-group-inputbox"> <label class="img" for="username"> <svg class="icon user-icon"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#user-icon"></use> </svg> </label> <input type="text" name="username" placeholder="Enter your name"> </div> </div> <div class="form-group"> <label class="text">Password</label> <div class="form-group-inputbox"> <label class="img" for="password"> <svg class="icon lock-icon"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#lock-icon"></use> </svg> </label> <input type="password" name="password" placeholder="Enter you password"> </div> </div> <div class="modal__form-bottom"> <div class="form-group"> </div> <div class="modal__form-box"> <button class="btn btn-orange" type="submit">Sign In</button> <span class="vertical-links"> <a href="https://kwebby.com/account/forget">Forgot Password</a> <a href="https://kwebby.com/account/resend">Resend Activation Email</a> </span> </div> <div class="modal__links"> <span>Not a Member? <a href="https://kwebby.com/account/register">Sign Up now</a></span> </div> </div> </form> </div> <div class="modal__bg"> <div class="modal__bg-logo"> <img src="https://kwebby.com/theme/nts/images/logo-orange.svg" alt="logo"> </div> </div> <div class="modal__close js-modal-close"> <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none"> <path d="M23.1296 21.4156L2.58501 0.871021C2.10422 0.390226 1.33074 0.38423 0.857337 0.857629C0.383939 1.33103 0.389935 2.10451 0.87073 2.5853L21.4153 23.1299C21.8961 23.6107 22.6696 23.6167 23.143 23.1433C23.6164 22.6699 23.6104 21.8964 23.1296 21.4156Z"/> <path d="M21.4151 0.870529L0.870533 21.4151C0.389738 21.8959 0.383742 22.6694 0.85714 23.1428C1.33054 23.6162 2.10402 23.6102 2.58481 23.1294L23.1294 2.58481C23.6102 2.10401 23.6162 1.33053 23.1428 0.857136C22.6694 0.383738 21.8959 0.389734 21.4151 0.870529Z"/> </svg> </div> </div> </div> </div> <div class="modal js-modal js-modal-signup"> <div class="popup__wrap"> <div class="modal__wrapper"> <div class="modal__form"> <h3 class="left-side-h3">Create Free Account</h3> <div class="top-section__title">Sign in using social network</div> <form action="https://kwebby.com/account/register" method="POST" class="loginme-form"> <div class="modal__socials social"> <div class="social-content"> <!--<a href="https://kwebby.com/facebook/login" class="social-btn social-btn--facebook" title="Sign in using Facebook">--> <!-- <span class="social-btn-icon">--> <!-- <img src="https://kwebby.com/theme/nts/images/facebook-white.svg" alt="">--> <!-- </span>--> <!-- <span class="social-btn-txt">Facebook</span>--> <!--</a>--> <a href="https://kwebby.com/google/login" class="social-btn social-btn--mail" title="Sign in using Google"> <span class="social-btn-icon"> <img src="https://kwebby.com/theme/nts/images/google-white.svg" alt=""> </span> <span class="social-btn-txt">Google</span> </a> <!--<a href="https://kwebby.com/twitter/login" class="social-btn social-btn--twitter" title="Sign in using Twitter">--> <!-- <span class="social-btn-icon">--> <!-- <img src="https://kwebby.com/theme/nts/images/twitter-white.svg" alt="">--> <!-- </span>--> <!-- <span class="social-btn-txt">Twitter</span> --> <!--</a>--> </div> </div> <div class="top-section__title">Sign up with your email address</div> <div class="form-group"> <label class="text">Username</label> <div class="form-group-inputbox"> <label class="img" for="username"> <svg class="icon user-icon"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#user-icon"></use> </svg> </label> <input type="text" name="username" placeholder="Enter your name"> </div> </div> <div class="form-group"> <label class="text">Email</label> <div class="form-group-inputbox"> <label class="img" for="email"> <svg class="icon envelop-open"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#envelop-open"></use> </svg> </label> <input type="text" name="email" placeholder="Enter your email"> </div> </div> <div class="form-group"> <label class="text">Full Name</label> <div class="form-group-inputbox"> <label class="img" for="full"> <svg class="icon user-icon"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#user-icon"></use> </svg> </label> <input type="text" name="full" placeholder="Enter your fullname"> </div> </div> <div class="form-group"> <label class="text">Password</label> <div class="form-group-inputbox"> <label class="img" for="password"> <svg class="icon lock-icon"> <use xlink:href="https://kwebby.com/theme/nts/icons/sprite.svg#lock-icon"></use> </svg> </label> <input type="password" name="password" placeholder="Enter you password"> </div> </div> <div class="modal__form-bottom"> <div class="form-group"> </div> <div class="modal__form-box"> <button class="btn btn-orange" type="submit">Sign Up</button> <div> Already a member? <a href="https://kwebby.com/account/login" style="color: #EF572C;">Login now</a> </div> </div> </div> </form> </div> <div class="modal__bg"> <div class="modal__bg-logo"> <img src="https://kwebby.com/theme/nts/images/logo-orange.svg" alt="logo"> </div> </div> <div class="modal__close js-modal-close"> <svg xmlns="http://www.w3.org/2000/svg" width="24" height="24" viewBox="0 0 24 24" fill="none"> <path d="M23.1296 21.4156L2.58501 0.871021C2.10422 0.390226 1.33074 0.38423 0.857337 0.857629C0.383939 1.33103 0.389935 2.10451 0.87073 2.5853L21.4153 23.1299C21.8961 23.6107 22.6696 23.6167 23.143 23.1433C23.6164 22.6699 23.6104 21.8964 23.1296 21.4156Z"/> <path d="M21.4151 0.870529L0.870533 21.4151C0.389738 21.8959 0.383742 22.6694 0.85714 23.1428C1.33054 23.6162 2.10402 23.6102 2.58481 23.1294L23.1294 2.58481C23.6102 2.10401 23.6162 1.33053 23.1428 0.857136C22.6694 0.383738 21.8959 0.389734 21.4151 0.870529Z"/> </svg> </div> </div> </div> </div> </footer> <!--- <script src="https://code.jquery.com/jquery-2.2.4.min.js" integrity="sha256-BbhdlvQf/xTY9gja0Dq3HiwQF8LaCRTXxZKRutelT44=" crossorigin="anonymous"> </script>---> <script defer type="text/javascript" src="https://cdn.kwebby.com/select2.min.js"></script> <script defer type="text/javascript" src="https://cdn.kwebby.com/slick.min.js"></script> <script defer type="text/javascript" src="https://cdn.kwebby.com/circle-progress.min.js"></script> <!-- <script defer type="text/javascript" src="https://cdn.kwebby.com/main.min.js"></script> --> <script defer type="text/javascript" src="/theme/nts/js/main.min.js"></script> <!-- Bootstrap --> <script defer src="https://cdn.kwebby.com/bootstrap.min.js" type="text/javascript"></script> <script defer type='text/javascript' src='https://cdn.kwebby.com/sweetalert.min.js'></script> <!-- App JS --> <script defer src="https://cdn.kwebby.com/app.min.js" type="text/javascript"></script> <!-- Mailchimp code --> <script defer src="https://cdn.kwebby.com/chimp.js" type="text/javascript"></script> <script> jQuery.event.special.touchstart = { setup: function( _, ns, handle ) { this.addEventListener("touchstart", handle, { passive: !ns.includes("noPreventDefault") }); } }; jQuery.event.special.touchmove = { setup: function( _, ns, handle ) { this.addEventListener("touchmove", handle, { passive: !ns.includes("noPreventDefault") }); } }; jQuery.event.special.wheel = { setup: function( _, ns, handle ){ this.addEventListener("wheel", handle, { passive: true }); } }; jQuery.event.special.mousewheel = { setup: function( _, ns, handle ){ this.addEventListener("mousewheel", handle, { passive: true }); } }; </script> <script defer src="https://cdn.kwebby.com/lazysizes.min.js" ></script> </body> </html><script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="8668a927ad88a395670c170a-|49" defer></script>