Project PSCMS - Perfect seo cms

Jakinollo

Registered Member
Joined
Nov 22, 2009
Messages
55
Reaction score
14
Hi all,
i'm not new to bhw, i've read a lot while posting a bit..

Anyway i'm a programmer and i'd like to know your opinion about a project i've in mind and that is coded in testing.

Project Perfect Seo cms

What?
It's a cms focused on gaining highest seo ranking possible, so seo comes before everything else.

Why?
I don't like wp, joomla and similar.. too heavy... too insecure ( i'm on a cyber security team i know what i say): so imho I prefer to write it from scratch. I want to be able to touch the application core in few time without need to study everything core team did on it.

Objectives
  • Amp
  • strucutred data
  • og meta and others
  • page speed insight 100/100
  • cache for fast delivery of pages and assets
Programming principles
  • Modularity
  • Extendibility
  • Expandability
  • Portability

Languages / Assets
  • bootstrap custom build (maybe v4 in the future)
  • jquery
  • backedn in php >7 written in cakephp or Yii

Status
UML : draft
code : achieved 100/100 on page insight with diferent templates

Availability
Project is in pre-alpha now, i will open to BHW members for testing when in alpha.

So?
I'd like to know if there are people interested, opinions, critics , ideas to continue the project or changing to semething else :)

Thank you!

This post will be updated with the infos.
 
Last edited:
  • what language / tech stack is used?
  • did you build the underlying fw yourself?
  • how many contributers work on the project?
  • what license will you use (smth GPL or BSD or what)?
  • if php what version?
    • what kind of bytecode cache engine will be supported
    • will ther be http caching
Which VCS do you use? Oh and which design pattern u gonna use?
 
  • what language / tech stack is used?
php > 7, draft is in cakephp for backend, maybe converted to Yii
  • did you build the underlying fw yourself?
sorry, what u mean by fw?
  • how many contributers work on the project?
me plus another if necessary
  • what license will you use (smth GPL or BSD or what)?
private code for now, it wont' be released until decision
  • if php what version?
    • what kind of bytecode cache engine will be supported
    • will ther be http caching

    caching will be done serving static html pages under nginx, assets by cdn
Which VCS do you use? Oh and which design pattern u gonna use?

git , gitflow , mvc
 
Last edited:
Framework

I'm not a fan of cake php - that may come from that I mostly worked with ZendFW and Symfony.
I guess cake ist missing DICs in their core?

ah ok sorry.. yeah.. cake or yii.. for dic there should be some plugin... anyway.. we will see if such implementation is needed.

BUT.. This post should be less tech anch more about SEO FEATURES and CONCEPTS it should implement. (thank u for your support :-)
 
Last edited:
ah ok sorry.. yeah.. cake or yii.. for dic there should be some plugin... anyway.. we will see if such implementation is needed.

BUT.. This post should be less tech anch more about SEO FEATURES and CONCEPTS it should implement. (thank u for your support :)

Thank u, but i need to know if this could be used by seo guys, if it's an interesting project or not..
 
I recommend these features:

Spinning support
Scheduled re-spinning of content
Spinning of syndicated content
Content subscriptions... (paypal subscription for spun versions of posts)

Integrated SEO reporting:
Target Terms for page
Referring URLs
Traffic
Match counts in page content
other on-page SEO KPIs
 
I recommend core functions from HideMyWP: custom folder and file name settings for less footprint.
 
The best CMS for SEO:
Helps search engines to properly read your website
Helps you to find and optimize content for the right keywords
Facilitates the sharing of content and social media
 
I recommend these features:

Spinning support
Scheduled re-spinning of content
Spinning of syndicated content
Content subscriptions... (paypal subscription for spun versions of posts)

Integrated SEO reporting:
Target Terms for page
Referring URLs
Traffic
Match counts in page content
other on-page SEO KPIs

mmmm..
I need to know the use case for the spinning feature.. do you want the cms to spin an article you submit, crete spinned articles from an original one? Keep in mind that this should be a high level cms, so spinning is good for seo, but could limit social share..
Anyway spinning support is not difficult to implement as content is modular.

PSCMS will have a built in keyword system to track keyword in relation with content. No problem to use analytics, or other external api like semrush (serp, kpi, ...).
 
I recommend core functions from HideMyWP: custom folder and file name settings for less footprint.

You mean if it would be used for building a pbn ... yeah it wont' have any particular footprint based on folders or file extensions... they are parameters that can be instanced on every installation
 
The best CMS for SEO:
Helps search engines to properly read your website
Helps you to find and optimize content for the right keywords
Facilitates the sharing of content and social media

- yeah it will be 100/100 page speed insight and amp ready, structured data ready
- content optimisation will be served by external api first, and so searching for low difficult keywords
- social share will be obviously embedded
 
mmmm..
I need to know the use case for the spinning feature.. do you want the cms to spin an article you submit, crete spinned articles from an original one? Keep in mind that this should be a high level cms, so spinning is good for seo, but could limit social share..
Anyway spinning support is not difficult to implement as content is modular.

PSCMS will have a built in keyword system to track keyword in relation with content. No problem to use analytics, or other external api like semrush (serp, kpi, ...).

The CMS should be able to render spintax... not create spintax... that is outside the scope. So in your schema you need to account for a spinable_version and a spun_version... where spun version is what gets displayed on page and cached. Then at scheduled times the CMS can respin the page... say every 7 days. Additionally anything going into a syndicated feed should be spun so that it is unique to the original. Finally create an option so other blogs can paypal subscribe to spun versions of your posts.

Then your CMS isn't just a component... it is a business.
 
The CMS should be able to render spintax... not create spintax... that is outside the scope. So in your schema you need to account for a spinable_version and a spun_version... where spun version is what gets displayed on page and cached. Then at scheduled times the CMS can respin the page... say every 7 days. Additionally anything going into a syndicated feed should be spun so that it is unique to the original. Finally create an option so other blogs can paypal subscribe to spun versions of your posts.

Then your CMS isn't just a component... it is a business.

ok, on todo list
 
You need to cover the track of this CMS to ensure Google or any search engine cannot identify which CMS it is, reason being it will be the most targeted CMS as a CMS used by SEOs will invite trouble from Google.
 
You need to cover the track of this CMS to ensure Google or any search engine cannot identify which CMS it is, reason being it will be the most targeted CMS as a CMS used by SEOs will invite trouble from Google.

yeah, anyway the main focus is gaining best google ranking without violating any google webmaster rule.
I really don't know if i should put a " pbn ready " on todo project..
The fact that it has frontend dependencies is a footprint itself..
 
yeah, anyway the main focus is gaining best google ranking without violating any google webmaster rule.
I really don't know if i should put a " pbn ready " on todo project..
The fact that it has frontend dependencies is a footprint itself..
To be honest you can never rank any site within Google ToS. You need to factor this in so that you don't leave out a majority of SEOs from using your CMS. As I understand it is being developed keeping in mind SEOs.
 
To be honest you can never rank any site within Google ToS. You need to factor this in so that you don't leave out a majority of SEOs from using your CMS. As I understand it is being developed keeping in mind SEOs.
ok, structure randomizing is on todo list
 
Back
Top