Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save martinbowling/2cbc90317ba41ab3c1a3b0bc13a65fec to your computer and use it in GitHub Desktop.
Save martinbowling/2cbc90317ba41ab3c1a3b0bc13a65fec to your computer and use it in GitHub Desktop.
Claude3-Opus-Chain-of-Though-HCU-Content-Classifier
<prompt>
<html-content>
<!-- Paste the HTML content of the webpage here -->
</html-content>
Now that the HTML content of the webpage is provided above, please analyze the webpage and evaluate the following features to determine if the content is likely to be helpful based on Google's guidelines. For each feature, indicate "Yes" if the feature is present and "No" if it is not. Use the following chain of thought process for each feature:
1. Identify the specific HTML elements and attributes related to the feature within the provided HTML content.
2. Determine if the feature is present on the page based on the identified elements and attributes.
3. Consider the implications of the feature's presence or absence in terms of user experience and Google's guidelines.
4. Assign a "Yes" or "No" value to the feature based on the analysis.
Features to analyze:
1. Fixed Ad - Footer: Check if there is an advertisement fixed to the footer of the page that scrolls with the user and may cover up the main content.
2. Fixed Video Ads: Look for auto-play video ads that follow the user while scrolling and may be difficult to dismiss, covering a significant amount of content.
3. Stock Images: Analyze image file names to determine if the page uses stock images or unoriginal images, including unaltered product or manufacturer images.
4. First-Person Pronouns: Count the number of first-person pronouns (e.g., "I," "we," "my," "ours") in the first 1000 words of the main content to assess if the content demonstrates personal experience.
5. Number of Ads: Count the total number of video and image ads on the page.
6. First-Hand Experience: Evaluate if the content demonstrates first-hand experience with the subject matter, such as unique images, videos, or personal anecdotes related to the topic.
7. Cookie Consent: Check if the page displays a cookie consent banner.
8. Notifications: Look for the presence of browser push notifications.
9. Mega Menu - Head: Check if there is a large, expandable navigational menu with 30 or more links at the top of the website.
10. Contact - Footer: Verify if contact information is clearly displayed at the bottom of the page.
11. Unclear/Missing Logo: Check if the site displays a clear logo, especially on mobile devices.
12. Search - Footer: Look for the presence of a search function near the bottom of the page.
13. Missing Contact: Check if the page lacks contact information entirely.
14. Any Contact: Verify if contact information is displayed anywhere on the page.
15. Any Mega Menu: Check for the presence of a mega menu anywhere on the page.
16. Number of Affiliate Links: Count the total number of affiliate links on the page.
17. Privacy Anywhere: Check if the page links to a privacy policy anywhere on the page.
18. Number of CTAs: Count the total number of calls-to-action on the page.
19. Search - Head: Look for the presence of a search function in the header of the page.
20. Any Author Info: Check if any author information is provided on the page.
21. CTA - Footer: Look for the presence of a call-to-action in the footer of the page.
22. Social Links - Footer: Check if social media links are present in the footer of the page.
23. Contact - Head: Verify if contact information is displayed in the header of the page.
24. CTA in Head: Look for the presence of a call-to-action in the header of the page.
25. Editorial Policy: Check if the page links to an editorial policy.
26. Word Count: Determine the total number of words in the main content of the page.
27. Copyright: Check if a copyright notice is present on the page.
28. Affiliate Disclosure: Look for the presence of an affiliate disclosure on the page.
29. Linked Author Page: Check if the page links to a dedicated author page.
30. Social Links Head: Look for the presence of social media links in the header of the page.
31. Active Comments: Check if there is an active comment section on the page.
32. Fixed Ad Head: Look for the presence of a fixed advertisement in the header of the page.
33. Mega Menu Footer: Check if there is a mega menu in the footer of the page.
34. Intrusive Interstitial: Look for the presence of intrusive interstitial ads on the page.
35. Fixed Scroll Nav: Check if there is a fixed scrolling navigation menu on the page.
36. Table of Contents: Look for the presence of a table of contents on the page.
37. About - Footer: Check if there is an "About" section or link in the footer of the page.
38. Author Links: Look for the presence of links to the author's website or social media profiles.
39. On Page Author Info: Check if author information is provided directly on the page.
40. Author Photo: Look for the presence of an author photo on the page.
41. About - Head: Check if there is an "About" section or link in the header of the page.
42. Descriptive Navigation: Evaluate if the navigation menu uses descriptive labels that clearly indicate the content of each section.
After analyzing all features, provide a summary of whether the content is likely to be helpful based on the presence or absence of these features, along with the reasoning behind the conclusion. Consider the following factors in the summary:
1. The overall balance of positive and negative features on the page.
2. The potential impact of each feature on user experience and perceived content quality.
3. The alignment of the page's features with Google's guidelines for helpful content.
4. The cumulative effect of multiple positive or negative features on the page's likelihood of being considered helpful.
Include the full table of features and their corresponding "Yes" or "No" values in the report. Use the chain of thought process to explain the reasoning behind each feature's value and the final conclusion on the content's helpfulness.
</prompt>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment