1-N
If you’re words and phrases are common and will be duplicated between many rows, you should consider separating them out into a 1-n relationship. That way searching and querying the data could be more efficient by joining them with your data. This may not meet your requirements – it totally depends on the type of words and phrases.
FULLTEXT
Indexing a varchar 1000 is a bad idea (I don’t like to make assumptions but this is generally always bad). Not only will this use a HUGE amount of memory and index space if your dataset grows it will be a hard performance bottle neck to fix when it starts to become an issue. This is the very reason FULLTEXT is there, if you’re using MySQL 5.6 or greater you can now use FULLTEXT on INNODB tables too – if you’re using an older version it will unfortunately only be supported in MyISAM and that storage engine has is downsides (some rather large ones so please research that before opting for it).
Proper search
The best solution would be to use a proper search engine such as Lucene, Sphinx or Xapian