My website has been on google for a few weeks now but I still get almost no clicks, my website is here. If you have any suggestions please leave me a comment or open a issue or pr at the github
Adding a couple of technical things I noticed after pulling your robots.txt and sitemap, since the content side is already covered above.
Your robots.txt has Disallow: resources/, and that folder is where nav.js and nav.html live. The navbar is injected by that script, so if Googlebot respects the rule it renders your pages without any nav links, and the blog posts are only discoverable through the sitemap. Google also expects robots rules to start with /, so the line is either ignored or doing exactly the wrong thing. There's nothing private in there, I'd just delete it. Even better, put the nav as plain HTML in each page so the links exist without JS.
The sitemap lists /index.html, /pynumerate/index.html etc., while your links point to / and /pynumerate/. Those are two URLs for the same page in Google's eyes. List the short versions in the sitemap and add <link rel="canonical" href="https://dev2023-op.github.io/"> (and the matching one on each page) so the signals don't get split.
After that, resubmit the sitemap in Search Console and use URL Inspection on a blog post to see what the rendered HTML looks like to Google.
Thanks — that homepage is basically a projects shell: one H1 and a single short card, so there's almost nothing for Google to match a query to. With ~31 impressions and position ~5 you're already getting a few looks; clicks stay low because the page doesn't answer a search intent in the first screen. Quick wins: pick one phrase people would actually type (e.g. "Pynumerate OSINT website scanner" or whatever the tool does in plain words), put that in the title tag + H1, add 2–3 short paragraphs on what it does / who it's for / how to try it, and give each project its own URL with unique title/meta. GitHub Pages is fine for indexing once the HTML has real copy. In Search Console, which query is driving those impressions — brand, tool name, or something else?
If Search Console is mostly showing queries around "tools", that fits the low click rate. Those words are broad, so even a decent average position usually loses to bigger roundups. I would aim the title, H1 and first paragraph at the specific job the project does (for example, scanning a site for OSINT data) and let "tools" live later in the copy. Give it a couple of weeks and see whether the query list shifts toward that phrase.
Being indexed isn't the same as getting clicks. Check Search Console → Performance: what queries show impressions, and what's the average position? If you're on page 2+, tighten the title/meta to match one clear intent per page, and make sure the page actually answers that query in the first screen. Also look at mobile speed and whether the homepage is mostly empty chrome with thin copy — Google rarely sends traffic to thin new pages. Which URL is the main landing page you care about, and what topic should it rank for?
Top comments (7)
Adding a couple of technical things I noticed after pulling your robots.txt and sitemap, since the content side is already covered above.
Your robots.txt has
Disallow: resources/, and that folder is where nav.js and nav.html live. The navbar is injected by that script, so if Googlebot respects the rule it renders your pages without any nav links, and the blog posts are only discoverable through the sitemap. Google also expects robots rules to start with/, so the line is either ignored or doing exactly the wrong thing. There's nothing private in there, I'd just delete it. Even better, put the nav as plain HTML in each page so the links exist without JS.The sitemap lists
/index.html,/pynumerate/index.htmletc., while your links point to/and/pynumerate/. Those are two URLs for the same page in Google's eyes. List the short versions in the sitemap and add<link rel="canonical" href="https://dev2023-op.github.io/">(and the matching one on each page) so the signals don't get split.After that, resubmit the sitemap in Search Console and use URL Inspection on a blog post to see what the rendered HTML looks like to Google.
thanks for the feedback
Thanks — that homepage is basically a projects shell: one H1 and a single short card, so there's almost nothing for Google to match a query to. With ~31 impressions and position ~5 you're already getting a few looks; clicks stay low because the page doesn't answer a search intent in the first screen. Quick wins: pick one phrase people would actually type (e.g. "Pynumerate OSINT website scanner" or whatever the tool does in plain words), put that in the title tag + H1, add 2–3 short paragraphs on what it does / who it's for / how to try it, and give each project its own URL with unique title/meta. GitHub Pages is fine for indexing once the HTML has real copy. In Search Console, which query is driving those impressions — brand, tool name, or something else?
mostly tools
If Search Console is mostly showing queries around "tools", that fits the low click rate. Those words are broad, so even a decent average position usually loses to bigger roundups. I would aim the title, H1 and first paragraph at the specific job the project does (for example, scanning a site for OSINT data) and let "tools" live later in the copy. Give it a couple of weeks and see whether the query list shifts toward that phrase.
Being indexed isn't the same as getting clicks. Check Search Console → Performance: what queries show impressions, and what's the average position? If you're on page 2+, tighten the title/meta to match one clear intent per page, and make sure the page actually answers that query in the first screen. Also look at mobile speed and whether the homepage is mostly empty chrome with thin copy — Google rarely sends traffic to thin new pages. Which URL is the main landing page you care about, and what topic should it rank for?
Thanks for the feedback, the main page is dev2023-op.github.io/index.html